Let’s get the AMAs kicked off on Lemmy, shall we.

Almost ten years ago now, I wrote RFC 7168, “Hypertext Coffeepot Control Protocol for Tea Efflux Appliances” which extends HTCPCP to handle tea brewing. Both Coffeepot Control Protocol and the tea-brewing extension are joke Internet Standards, and were released on Apr 1st (1998 and 2014). You may be familiar with HTTP error 418, “I’m a teapot”; this comes from the 1998 standard.

I’m giving a talk on the history of HTTP and HTCPCP at the WeAreDevelopers World Congress in Berlin later this month, and I need an FAQ section; AMA about the Internet and HTTP. Let’s try this out!

  • kromem@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    What’s the funniest legitimate non-joke standardization detail you’ve come across?

    • Two9A@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

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

      • SpinDrift@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Can someone elaborate on this please?

        Edit: oh jeez. I’m so used to reading “referer” I didn’t even realize it was a typo.

      • qwop@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I’d be happy if we’d just accepted “referer” as the correct spelling for everything, but instead we have the “Referrer-Policy” header, so now I need to check the correct spelling for anything involving referring…

        I do sort of like the idea that because we want to keep backwards compatibility on software we just change the language instead since that’s easier.