There was even an entire standards document drawn up (as a practical joke), called the Hyper Text Coffee Pot Control Protocol (HTCPCP 1.0). To this day though, there the server status response 418 - I’m a teapot still exists. It was defined as part of HTCPCP as the error code returned when you tried to get a teapot to brew coffee :)

Web nerds took their coffee seriously! Or maybe they didn’t? Does doing up an entire standards document as an april fools joke count as serious or unserious?

That’s serious unseriousness, or in other words German humor
German humor is nothing to laugh at.
German… what now?
I’m not laughing.

Humorous RFCs and protocol proposals are an ancient internet tradition: en.wikipedia.org/…/April_Fools'_Day_Request_for_C…

Engineering humour of this sort actually goes back even further – en.wikipedia.org/…/April_Fools'_Day_Request_for_C…

Nerdy humour has probably been around as long as there have been engineers.

April Fools' Day Request for Comments - Wikipedia

Learning about computer science and finding all the subtle jokes embedded in the naming conventions is peak. These nerds had humor!
Google also has this little easter egg: www.google.com/teapot
Geeking out over the origins of HTTP 418 kinda got me a job once. But that was back when that kind of stuff, connecting interpersonally with the humans that you work with, mattered during hiring.

connecting interpersonally with the humans

You could’ve stopped right there and it would’ve still made sense, which is sad.

Glad my lore has served you well.

Does doing up an entire standards document as an april fools joke count as serious or unserious?

It’s impossible to know until you observe them. They’re Shrödinger’s Nerds.

Nerds making joke standards is nothing unique.

See also: IETF RFC 1149 and IPoAC

IP over Avian Carriers - Wikipedia

Another example of such an attack

CW: animals being eaten

that’s not a man-in-the-middle attack (unless the bird is a trained falcon or something), it’s packet loss due to infrastructure damage

Valid. I checked again, and:

Known risks to the protocol include:

  • Carriers being attacked by birds of prey. RFC2549: “Unintentional encapsulation in hawks has been known to occur, with decapsulation being messy and the packets mangled.”

So I guess that’s what’s happening here

I get no respect.
All you had to do was brew a coffee…