I loved the way people were calling it the X Bone from halfway through the release announcement.

You and the rest of the internet, that’s why they shut down that Discord server.

In my experience, badly.

Computers have had the capability to automatically execute nearby bats for years, just run autoexec.bat

I mean, it got that error in class_5699.method_65313 so it’s not like it isn’t obfuscated at all.

There’s probably a lot of people on ‘stable’ distros who are still running Wayland code from a couple of years ago and hitting bugs that have been fixed already.

I feel like a lot of people tried Wayland in 2020, a bunch of things didn’t work and they’ve been permanently traumatised.

I switched my laptop years ago, but my desktop only fairly recently - multi screen, mixed DPI with variable refresh rates for gaming took longer to be ready than my laptop’s single screen, normal DPI, fixed refresh rate config.

If you deal with the fundamental problems of the protocol itself and also provide backwards compatibility… Congrats, you’ve just reinvented Wayland and XWayland.

Dealing with X11’s problems while still being X11, when X11 is the problem? Yeah, I wouldn’t hold my breath either.

the ICQ age

There’s a blast from the past. Uh oh!

IIRC TRIM commands just tell the SSD that data isn’t needed any more and it can erase that data when it gets around to it.

The SSD might not have actually erased the trimmed data yet. Makes it even more important to turn it off ASAP and send it away to a data recovery specialist if it’s important data.

Even if it’s a completely valid address and the domain exists, they still might’ve fat fingered the username part. Going to extreme lengths to validate email addresses is pointless, you still have to send an email to it anyway.

Don’t be ridiculous, I’m going to use an open source password manager to fill an IPv6 address for my email server into the DoorDash signin page.

I wouldn’t say I was friends with Windows. It’s more like escaping an abusive relationship IMO.

port forwarding/firewall issues that most people don’t know how to deal with

This sort of thing makes me want to tear my hair out when I hear “Why bother rolling out IPv6 when IPv4 just WORKS!?”

NAT, port forwarding and the problems they cause are seen as expected, just the way the internet works instead of the dirty hacks they actually are. Most people aren’t old enough to remember the time when everything connected to the internet had a routable IPv4 address.

It generates an answer that looks correct. Actual correctness is accidental. That’s how you wind up with documents with references that don’t exist, it just knows what references look like.

At least they aren’t trying to get Steam to work on Kali.

You couldn’t crank your CPU in the olden days, it’d make games run in fast forward.

Nobody wants to deliberately use the wrong compression type when extracting, so modern tar will figure out the compression itself if you just point it at a file. So tar -xf filename works on almost anything. You don’t need to remember which flag to use on a .tar.bz2 file and which one for a .tar.xz file.

And we’re pronouncing it JIMP?