A VPN encrypts traffic between your device and the VPN server, and any packet on that path includes your IP address. So anyone attempting to decrypt your VPN traffic can trivially distinguish your packets from other users of the VPN server.
See also https://lemmy.world/u/p1mrx
A VPN encrypts traffic between your device and the VPN server, and any packet on that path includes your IP address. So anyone attempting to decrypt your VPN traffic can trivially distinguish your packets from other users of the VPN server.
So your threat model assumes an actor with a quantum computer capable of breaking RSA, but not a regular computer capable of filtering by IP address?
Worth noting: “Visible includes mobile hotspot with unlimited data at speeds up to 5Mbps.”
Follow https://github.com/mifi/lossless-cut/issues/818 to be notified if lossless-cut ever gets an Android port.
Here is the building on Street View:
It’s been knocked down and replaced since 2015.
I listed the 5 possible digits. What’s missing?
IPv6 subnet masks are long, but super easy because of hexadecimal. A bunch of F
s, then [
then a bunch of ]?0
s.
That patch was my only contribution to Firefox, and I didn’t research how to update the user-facing changelog. When 122 hits my phone I’ll ping the bugs, to notify the 20 nerds who actually care about the problem. Typing IPv4/IPv6 literals is a pretty niche feature on the modern web.
Currently https://play.google.com/store/apps/details?id=org.mozilla.firefox says “Version 121.1.0, Updated on Jan 19, 2024”
There were some pull requests to fix that, but guys at Mozilla said that those pull requests lead to performance regressions and rejected that.
The latest PR was accepted in November, so IPv6 literals work in v122 alpha.
Keyboard shortcuts are not relevant, because I’m referring to the mouse-only zoom interface.
I’ve added support for Ctrl/Command/Shift in v1.7, but the menu text is unchanged because I don’t know which keys are pressed prior to the click event. This matches Chrome’s behavior.
‘New Tab’ is the default/only behavior currently.
I notice that Chrome supports Ctrl-click (background tab) and Shift-click (new window), and Firefox provides a modifiers array, so I think I could replicate this.
When I highlight the trailing lemmy.ml and select Open Link in New Tab, Firefox takes me to https://sh.itjust.works/c/firefox@lemmy.ml (the original link target) instead of https://lemmy.ml
I don’t think .co versus .com is the relevant factor. I can select xample.co by itself, but not as a substring of http://www.example.com. The rules seem so arbitrary and context-dependent that it behaves more like a dice roll than a usable feature.
If a selection to URL feature cares about TLDs, IP addresses, or text beyond the selection range, then it’s operating at the wrong abstraction layer. (well, technically Goto foo has a couple lines of code to [bracket] bare IPv6 addresses, but that’s not core functionality.)
That doesn’t work in many cases, like the example in the screenshot.
Firefox’s ‘Open Link’ feature is quite limited compared to Chrome. For example, try navigating to lemmy.ml using the “Firefox@lemmy.ml” link in the sidebar.
Even in cases where it works, it doesn’t preview the link target in the context menu.
Interesting, that does appear to solve the same problem.
In my decades of using web browsers, I can’t say that I’ve ever tried dragging text to the address bar. That’s not very discoverable, and the drag action messes with the page’s scroll position.
Hooray! Previously Firefox MV3 extensions had to include a custom button in the UI to prompt the user for host permissions at runtime. It generally made more sense to stay on MV2 than switch from a 2-click to a 6-click install procedure.