orangeboats @ orangeboats @lemmy.world

Posts

0

Comments

209

Joined

2 yr. ago

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.

The IDs of criminals are sometimes leaked on the web. People use those leaked IDs to register their account. Many systems don't actually check whether the ID is already registered, it works as long as the ID itself is valid.

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

"Shits me to tears" lmao that's amazing, I am gonna use it from now on.

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.

If I remember right, the syncing issue was particularly egregious when you run windowed X11 programs on Wayland. So it could be that you got lucky.

I think if you consider anything post C++03 (so C++11 or newer) to be "modern C++" then Concepts must be the top example, doesn't it?

Counting from C++0x that's almost a decade of waiting.

It's the explicit sync protocol.

The TL;DR is basically: everyone else has supported implicit sync for ages, but Nvidia doesn't. So now everyone is designing an explicit sync Wayland protocol to accommodate for this issue.

You need to enable DRM KMS on Nvidia.

Mine is simply default KDE. The only visible thing I've changed is the wallpaper -- changes to my desktop mostly concentrate on the "invisible" ones like shortcut keys or setting changes or scripting.

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

Desktop? I settled on Arch and Fedora.

Server? Debian. Although technically I never distrohopped on servers, been using Debian since the beginning of time.

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).

Ackshually you still can blame Windows for not supporting live updates.

Exclusive we is actually found in many languages, but usually it's the listener who is excluded. Malay kita "we" includes the listener, kami excludes the listener.

One with everything will be far more expensive than millions with one thing, and if you disagree with the service you wouldn't be able to switch to another one.

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