Assuming the entire US court system isn’t in the corporate pocket
I love your optimism
Assuming the entire US court system isn’t in the corporate pocket
I love your optimism
People who do work for themselves
Did you notice that I said “merge request” earlier? Your neighbours were kindly helping you to make a cake and you responded to their kindness with GTFO.
Did I say “some”? I think I did.
GNOME developers seem to have some sort of a weird “vision” for their software. If your bug report falls within their vision, good for you. When your bug report doesn’t, it’s insta WONTFIX.
The FDO icon theme fiasco occurred merely a few days ago.
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?
Neither hit the backdoor. Arch didn’t patch OpenSSH and the library wasn’t linked as a result.
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.
Probably not wrong. But it’s a double edged sword, if Tachiyomi wasn’t hosted on Github it’s likely that it wouldn’t have gotten this far.
It’s harder for other devs to discover your project when you use the other Git forges (e.g. Gitlab).
I am using it now as I’m commenting.
Been using it daily for years at this point.
And that’s why the MTU is typically 1500 bytes for Ethernet
TOML isn’t elegant at all but damn, it is really simple.
“it just maxes out the ram and then does nothing.” is absolute nonsense. The programs need memory to operate.
If your RAM is maxed out and the programs seem to operate just as fine, the OS is doing something behind the scenes, it’s just a matter of what that something is. And memory swapping / virtual memory is a well-known method of alleviating RAM overuse, at the cost of murdering your SSD/HDD lifespan.
Tell me you haven’t seen people adamantly defending IPv4 without telling me so…
Good luck getting a block of IP addresses from your regional internet registry for this community ISP… IP address exhaustion is just that, no more addresses. That’s why we are sharing them.
We do have a solution and it’s called IPv6, but its deployment is still not as widespread as people would like to be. If I self-host my website on IPv6, a lot of people from Europe would still be unable to access it.
That’s pretty much just pushing the centralization from Google, AWS etc to the hosting services.
It’s pretty difficult nowadays to self-host websites when everyone and their nanny shares a single public IP address (IPv4 address exhaustion is real, everyone!) unless you purchase a hosting service.
Tell me you know nothing about Chinese EVs without telling me you know nothing about Chinese EVs. BYD’s best sellers are actually plug-in hybrids, which is in no way “stolen” from Tesla.
Lots of social medias require a phone number nowadays. If you don’t add a phone number, at best they annoy you everyday to “secure your account”, at worst you can’t even login.
It sucks.
I use IPv6 exclusively for my homelab. The pros:
No more holepunching kludge with solutions like ZeroTier or Tailscale, just open a port and you are pretty much good to go.
The CGNAT gateway of my ISP tends to be overloaded during the holiday seasons, so using IPv6 eliminates an unstability factor for my lab.
You have a metric sh*t ton of addressing space. I have assigned my SSH server its own IPv6 address, my web server another, my Plex server yet another, … You get the idea. The nice thing here is that even if someone knows about the address to my SSH server, they can’t discover my other servers through port scanning, as was typical in IPv4 days.
Also, because of the sheer size of the addressing space, people simply can’t scan your network.