Welcome to Incremental Social! Learn more about this project here!
Check out lemmyverse to find more communities to join from here!

orangeboats

@orangeboats@lemmy.world

This profile is from a federated server and may be incomplete. Browse more on the original instance.

orangeboats ,

I bought a 3DS during Covid.

10/10 would recommend, especially Bravely Default!

orangeboats ,

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?

orangeboats , (edited )

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.

orangeboats ,

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.

orangeboats ,

Neither hit the backdoor. Arch didn't patch OpenSSH and the library wasn't linked as a result.

orangeboats , (edited )

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.

orangeboats ,

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.

orangeboats ,

I have seen it before on various social medias. Some are mad about their slang ("frfr" or that skull emoji), others being mad about their memes and some such.

Funnily enough, I saw pretty much the same comments being thrown on millennials during the 00s.

Some things never change.

orangeboats ,

I assumed it to be so. Maybe a "late zoomer" thing?

Linux market share passes 4% for first time (arstechnica.com)

We see the nearly 33-year-old OS’s market share growing 31.3 percent from June 2023, when we last reported on Linux market share, to February. Since June, Linux usage has mostly increased gradually. Overall, there's been a big leap in usage compared to five years ago. In February 2019, Linux was reportedly on 1.58 percent of...

orangeboats ,

It's just a notable milestone. For as long as I can remember Linux marketshare never went above the 3.something% mark.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • incremental_games
  • meta
  • All magazines
    •