Ancient IETF 'teapot' gag preserved for posterity as a standard

Instant of Tetleys?

At least 2000 perforations in that set up?

more important than ever

Shirley the need for a 418 response is more justified than ever before given the vast growth of IoT interconnectivity.

If you've ever

consumed a mix of tea and coffee you know why this error is needed. I still feel sick 40 years after the experience, any time I'm reminded of it.

Can't we just reserve 499 for extensions?

Make that a code for an extended error, where old implementations that only look for three digit codes will not get the full information, where those that do will see something like "499 extended error 49912345 actual error text" and drop the first part.

Trying to deprecate existing errors, even ones included in jest, is just going to cause confusion. Especially when haven't run out yet.

killing off the fun bits . . .

If all the fun bits are taken out of all of IT, it will really belong to the penpushing beancounters.

We are almost there, and when we arrive, coding will be 6Sigma'd and all these wasteful indentations that only cost storage space, obviously, duh, and all these extra protocols like tcp (to be replaced with a 'get it right first time, every time' strategy and a penalty for dropped packets) will have to go because they're in the way of improving efficiency.

RIP ddate.

ahe

As mentioned elsewhere

The humourless ones are taking over.

ddate was recently removed from linux-utils

The manpage for tune2fs has had the "You can tune a filesystem but you can't tuna fish" comment removed.

*sigh* :(

Joy removal 101

This sounds like a tech lead I had at a previous job. When writing documentation I always try and be slightly humorous, usually in the opening introduction. My reasoning is if you're having to read boring work docuemtnation then starting with a smile will put you in a better frame of mind.

I never do anything 'offensive' and would never compromise the documentation for the sake of being funny; it's a technique I've used for years when and has generally gone down well, for example we had a process that would occasionally fail on certain records, so I opened the 'How to fix this occasional issue' page with 'If, after looking behind the sofa and checking very hard behind the fridge you still can't find the data.......'

The tech lead at the time didn't like it apparently, although he'd never mention it, or have the decency to raise it with me I would often find all trace of humour and individuality removed without any comment whatsoever. This made me a little sad. (Never quite understood people who think work should be fun free, it's where I spend most of my time ffs.)

I did usually put the humour back though, often with slightly increased surrealism.

Obligatory

https://http.cat/418

(also, for you heathens who prefer dogs, https://httpstatusdogs.com/418-im-a-teapot )

Millennials don't actually ruin everything. Once Baby Boomers have consumed and destroyed whatever was in their path, they just often happen to be next on the scene.

At that point the Baby Boomers wipe the blood from their fangs and say, "Look what you've done!"

And then there was sigmonster ...

Ah yes, the old days when a little humour was always just a tap away ... I still keep these little oddities on my screen ... cookie monster

Has anyone implemented RFC 2324 or 7168

I know some mad scandinavians managed IP over avian carriers, but has anyone actually tried HTCPCP or HTCPCP-TEA