Scoopta

That's unfortunate

Even the article description is misleading, none of this is new, the only new bit is 64 bits which is cool I guess?

I would think that elogind should work? Is it hard dependent on systemd or logind? I thought it was the latter

Yeahhh, unfortunately I have friends that I can't talk to anywhere else and won't move. I'm not in the UK so it's not an immediate concern but it seems to slowly be coming for everyone

This is definitely interesting, a lot of work to setup given I normally just use the built in frontend for llama.cpp though. I also don't use LLMs for anything serious, but I might give it a go. I do love the vodka joke though. When life gives you potato, make vodka.

Discord in particular is a huge sore spot for me so this sucks :/. It's one of the few services I can't just leave

Depending on which accounts we're talking about some services like google use a rotating session identifier where if it rotates while in one browser and you open another browser using an older version of same session token it'll kick you out because it's expired. I know it happens if I rollback a snapshot of my profile even just like 24 or so hours. But ALL accounts, yeah I'm not sure there either

...I had never noticed this until now lol

Same although for a totally different reason. There are some services that really don't like gtlds and they will say your address is invalid if it doesn't end in .com, .net, or .org...all my serious domains are gtld...so some services have emails on meme domains because the only domains I have with traditional tlds are memes

🤔 how does one nuke a network of interconnected networks? The internet isn't a single entity. On another note, sorry for over analyzing the joke XD

Reading the README on the GitHub is amazing. I love the energy of this project if nothing else

Historically it used to be running on my local router/firewall and the pure v6 was just between my devices and that firewall. However my setup has changed considerably since then and nat64 has been moved to a VPS out of my normal network path because I got my own public v6 space. So my current setup is basically firewall -> VPN -> VPS with BGP for normal(v6) internet comms. That whole path is pure v6 and then in the same datacenter as that BGP VPS is my NAT64 VPS. Beautiful thing about NAT64 is you don't actually need it local if you don't want. There's even a fully public service for free if you don't want to setup your own and don't mind the tradeoffs (bad latency, shared IPs, low bandwidth) https://nat64.net/.

If it goes down for some reason I just lose access to websites that don't normally have AAAA records, which sounds like a big loss but honestly I've been running NAT64 in some capacity since 2019 and so over time I have sort of black balled services that don't have v6 in favor of ones that do so very little of my normal online activity normally needs v4. I actually have packet counting on my firewall tracking the amount of data exchanged with various large services, Google, Cloudflare, etc, my NAT64 VPS is one of the things it tracks and compared to my total traffic the NAT64 traffic is a very small <10% of my normal internet usage at this point.