Wow, Europe, you guys sure are worrying us a little.
-- Best regards, South East Asia
Assuming the entire US court system isn't in the corporate pocket
I love your optimism
But personal files are... personal?
Research journals are published. Public.
I still don't quite get why some people are defending manufacturers which remove the headphone jack on their phones...
3.5mm jacks don't cost much materially. Removing it doesn't bring any benefit at all, and you are forced to buy a bluetooth headphone or a Type-C-to-3.5mm dongle on top of that.
Entitled brat? What... Have you ever seen how GNOME developers respond to some bug reports and merge requests?
Since when has reporting bugs and contributing to the project become an entitlement?
I've noticed that many Reddit users with the username format Word_Word_Number (for example Absolute_Bot_1230) are almost guaranteed to either be a bot or extremely inflammatory -- it's like everything they post is meant to generate controversies.
Society in general encourages and rewards those who speak more, even if the things they speak have zero contribution or are absolute nonsense.
This also explains why VPN is a possible workaround to this issue.
Your VPN will encapsulate any packets that your phone will send out inside a new packet (its contents encrypted), and this new packet is the one actually being sent out to the internet. What TTL does this new packet have? You guessed it, 64. From the ISP's perspective, this packet is no different than any other packets sent directly from your phone.
BUT, not all phones will pass tethered packets to the VPN client -- they directly send those out to the internet. Mine does this! In this case, TTL-based tracking will still work. And some phones seem to have other methods to inform the ISP that the data is tethered, in which case the VPN workaround may possibly fail.
Not sure if it's still the case today, but back then cellular ISPs could tell you are tethering by looking at the TTL (time to live) value of your packets.
Basically, a packet starts with a TTL of 64 usually. After each hop (e.g. from your phone to the ISP's devices) the TTL is decremented, becoming 63, then 62, and so on. The main purpose of TTL is to prevent packets from lingering in the network forever, by dropping the packet if its TTL reaches zero. Most packets reach their destinations within 20 hops anyway, so a TTL of 64 is plenty enough.
Back to the topic. What happens when the ISP receives a packet with a TTL value less than expected, like 61 instead of 62? It realizes that your packet must have gone through an additional hop, for example when it hopped from your laptop onto your phone, hence the data must be tethered.
It's the fear of centralization, I believe (correct me if I'm wrong!).
Seeing that the whole point of federation is to decentralize the web, putting everything under the Cloudflare umbrella goes against this philosophy.
Awesome! I don't have a Discord account (well, I had) so this will be very useful.
If proper SATA ever goes away, I'd wager that there will still be SATA-to-USB adapters on sale. Heck, people still find ways to connect floppy drives to their modern PCs.