To be fair it’s 2024 and I’m still doing this, because adding an alternate location to install flatpaks in results in Flatseal not being able to detect those apps or edit those permissions. Just setting the default location as a symlink to where I want to magically fixes everything.

Yeah I’ve heard about punycode. Personally, I’m well against it because it puts down non-MURRICAN English domain names as second-class citizens on the internet. If I have a website about Copiapó, a perfectly legal town, there’s no good reason why the domain name should not be copiapó.cl rather than copiap-xcwhngoingohi4oleleiyho42yt4ptg4ht4.cl, making it look “suspect” and “malware-y”.

There were quite some complains back in the time about Firefox choosing not to “flag” internationalized names as potentially dangerous, and pretty much all those complaints that I know of likely came from English speakers who simply can’t understand other countries in the world even can have different alphabets.

And don’t get me started on TLS certificates in local networks…

I hate this and the fact that modern platforms seem to require TLS even if you’re serving localhost, so much.

I’ve taken to using .here (or .aqui, “here” in Español, much harder to match outside) as alternatives until something better comes up.

Ideally I’d use .aquí, correctly with the diacritic, but DNS doesn’t seem to support even the basics of Unicode in 2024.

64-bit IPv5

64-bit IP would be IPv8, not IPv5.

Not a big deal. We’re projected to run out of years by 2000 and then the world will end.

I felt dirty!

“Senpai, route me like one of your French ISPs”

128 bits basically gives one ip4 address space to each square meter of earth.

That sounds like terminal stage capitalism to me. Why would we want every tree in the Amazons to be cybergorized with its own IP? I don’t know Rick, 64 kbits bits ought to be enough for everybody, and I’m already risking it.

IPv6 is unfortunately not six bytes, no. For some weird, ass-backwards reason.

Boy do we like it!

That’s what they thought for IPv4… and for 2-year digits… and for…

1.1.1.1? :p

SQL uses it but yeah, not programming language :p.

I was on mobile so I didn’t have a .XCompose available to type ≠.

The fun thing is that, C++ being C++, this is actually an std::overflow_error…

This is potterdung’s ultimate plan.

Word! The whole snafu with co_routines has been quite the laughable show. It would have been trivially sortable if C++ did something like what PHP did, using a symbol to absolutely disambiguate what is a variable and what is not. That way eg.: await is a keyword, $await is a variable (perhaps a functor).

To make it even better, $ is already unused in C++!

Many Rust shills seem to have some rust in their brain…

You are technically correct. The best kind of correct.

Aren’t they powered by the sheer spite they generate at hearing the loudspeaker?

Because I left Windows precisely to avoid the kind of shittery that systemd is doing.

It’s absolutely no coincidence that the people who have developed the stuff that’s brought the most degradation to Linux - systemd, PulseAudio, Gnome’s “user has no right to themes” attitude - all come from a Microsoft background or explicitly work for Microsoft.

I’d have far less of a problem if systemd was split into more practical, actually independent things that actually worked and distros didn’t buy their snake oil so easily. But for the time being, to me, the systemd experience is pretty much like the PulseAudio experience, what with the whole “waiting 120 seconds for a network interface to activate that it’s not going to because it’s the damn ethernet port and I’m on the road so the cable is not connected, stupid letter-potter dipshit”.