you are viewing a single comment's thread
view the rest of the comments
[–] 178 points 5 months ago (7 children)

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?

  • source
  • hideshow 14 child comments
  • [–] 64 points 5 months ago* (1 child)

    Humorous RFCs and protocol proposals are an ancient internet tradition: https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments

    Engineering humour of this sort actually goes back even further -- https://en.wikipedia.org/wiki/Turbo_encabulator

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 38 points 5 months ago (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 14 points 5 months ago (3 children)

    That's serious unseriousness, or in other words German humor

  • source
  • parent
  • hideshow 6 child comments
  • [–] 5 points 5 months ago (1 child)

    Nerds making joke standards is nothing unique.

    See also: IETF RFC 1149 and IPoAC

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 5 months ago (1 child)
  • [–] 3 points 5 months ago (1 child)

    Another example of such an attack

    CW: animals being eatenimage

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 months ago* (1 child)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 5 months ago

    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

  • source
  • parent