Calling the SEC on Ea-Nașir over here…

418 is always a little disappointing though. Lots of projects out there touting their “full HTCPCP compatibility” when all they do is serve 418 to every request; no actual coffeepots I could find last time I looked.

Right, I self-host email and have done for ten years or more, but I don’t do it out of a server at home. Does my Postfix not count as selfhosting any more?

As I understand it, ricing a machine is to excessively modify it to achieve more speed, users of Gentoo being the origina ricers in the Linux world.

The term itself has dubious and arguably racist origins, in the world of modification of Japanese cars for street racing.

Sounds like HowToBasic (or Basics?), from memory.

So this came up with this user a few days ago, and apparently ð fell out of use later in Old English and its usage was merged into þ for hundreds of years.

I remain unconvinced.

Whenever I come across ASCII art in the comments, it’s a good day. Here’s one from the day job:

My leatherman was a little over a ton That thing must be huge!

Appreciate the linguistic lesson, thanks. I’ve always run on the modern Icelandic definition.

Appreciate the commitment to use of the thorn, but you know þ and ð are different sounds, right?

“þrough ðe Earþ” etc.

I’ve actually written exactly that before, when I needed to check the lowest bit in an SQL dialect with no bitwise operators. It was disgusting and awesome.

There’s a short story (more of a novella) by Stephen Baxter on this exact topic, for what it’s worth. Touching Centauri: https://www.e-reading.mobi/chapter.php/1035265/30/stephen-baxter-phase-space.html

He/she is an interesting special case, as Mandarin didn’t really have those as separate concepts until they were imported from Western languages; even now, they’re pronounced the same. So I can understand your friend’s confusion.

This is Settled: https://xkcd.com/1235/

A little lower down the stack, I always liked the Evil Bit in TCP, a standard which removes all need for firewalls heuristics by requiring malware or packets with evil intent to set the Evil Bit. The receiver can simply drop packets with the Evil Bit set, and thus be entirely safe forever from bad traffic.

At the physical interface layer where data meets real life, I especially enjoy IP over Avian Carrier; that link in particular is to the QoS definition which extends the original spec for carrying packets by carrier pigeon.

The incident you mention is probably the most impactful, but there’s also the time the Russian military blocked IPs outside Russia by returning 418 instead of the more logical 403.

I enjoy that the original draft for the Referer header spelled it wrong, and now we’re all stuck with the typo forever…