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!

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

      I think it’s excellent out here. I was stuck on Reddit for the longest time, and this recent debacle has pushed me to explore the networks at the edge; this feels a lot more like the Internet of old. The analogy of email is apt, I think, with the accounts on multiple servers and the interplay between.

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

      You’d have to catch up with Mr Masinter to get his opinion on adding error 418, I’m afraid; that piece of the business wasn’t my work.

      I’m happy it’s there though: it may have sparked flamewars, but at this point what hasn’t. It does bring somewhat of that sense of humanity to the whole enterprise of working on the Internet.

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

        I remember when I learned about this, I was working on an absurdly large project on my own. I was lost in all the details and losing hope of ever finishing. I was working on the backend API when I learned of this and took the time to implement the 418 response. It felt silly and brought the fun back to the project.

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

        I remember when I first learned of error 418 and it did really help me understand that the Internet as we know it was made and shaped by regular people with senses of humor. Helped make it seem a bit less daunting/intimidating to understand.

        It reminds me of how the Network Port 666 is specifically reserved for doom, always love Easter eggs like that in officially used protocols.

  • z3rOR0ne@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I just found out about this on Brodie Robertson’s yt channel! I am not a teapot btw!!

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

      Glad to hear it, you should walk around with a HTTP 418 hat so more people know you’re not a teapot.

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

    Was RFC 7168 written with Captain Picard’s tea Earl Gray, hot in mind? If not, are follow up modifications planned?

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

      So replicators are kind of a special case: they can make anything already fully prepared, without the need for a brewing command to be sent. It’s possible that by the 24th century, there’s a compatibility layer between Replicator Intermediate Language and HTCPCP, but I’ll leave that to future generations to establish.

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

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

    • Two9A@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      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…

      • qwop@programming.dev
        link
        fedilink
        English
        arrow-up
        0
        ·
        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.

      • SpinDrift@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        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.

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

      I quite like the idea of HTTP 256 Binary Data Follows, which is just 200 OK but you asked for a non-text content type file.

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

    I’m actually going to that conference! What’s the title of your talk? I’ll be sure to attend it!

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

      Excellent. I’m on Stage 4 on the Thursday afternoon: “Brewing Tea Over The Internet”.

      Should be fun times, see you there.

  • Clav64@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    I loved sharing this with my senior who hadn’t seen it before, and it gave our small team a Ggod chuckle one afternoon. Thanks for your creation.

    With the absence of a crystal ball, but with excellent inner knowledge, what future standards could you see being implemented in the next 10 years for internet?

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

      As it turns out, one of the Apr 1st RFCs for this year covers AI Sarcasm Detection, but I can see more serious protocols arising for the transfer of AI model data and/or training procedures in the coming years.

      I’d also hope ActivityPub reaches Internet Standard level, though it may fall outside the IETF’s scope of operations.

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

      My endorsement is at the bottom of that page, in fact. I wasn’t an active campaigner, but a word in favor was the least I could do.

      • Deebster@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Oops, RTFM. Well, thanks for fighting the good fight with the power of your reputation.

  • 200ok@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Every once and a while I’d just like to see 200 get some love, but no. It’s all 404 this, 502 that.

    I’m just “OK”. It’s like being the middle child of response codes.

  • Fenzik@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    What’s the most impactful 418-related incident you’ve witnessed? I remember a few years ago npm went down and was returning 418 which spawned jokes and chaos across the web

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

        I know russian a bit and jargon for russian word “teapot” is also commonly used as “dummy” or “novice”. 418 for foreigners might have been on purpose there which brings Your April’s fool joke to a nation wide level :)

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

      Out.

      Can’t stand pineapple at the best of times, on pizza is another level of wrong.