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
    37
    ·
    1 year ago

    This is actually a good use of 418 in production, and one I’ve come across before: if you need to perform some custom handling and throwing a HTTP error is the only sensible way to do it, 418 is always available.

    Unless your server really is a coffeepot, which is …unlikely.

      • Spaceman Spiff@lemmy.fmhy.ml
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 year ago

        Nah, coffee pots are strictly clients in the world of tomorrow. They connect to a (datamining) cloud service, and you control it through an app.

        • SturgiesYrFase@lemmy.ml
          link
          fedilink
          English
          arrow-up
          6
          ·
          1 year ago

          Let’s be real…that’s the world of today. The world of tomorrow will either be more intrusive, or we’ll be talking to children around a fire about this wonderful drink made from beans that woke you up in the morning. And they won’t understand what we’re talking about, because the only other forms of life that survived are roaches, a godzilla sized Cher, and a burgeoning race…a new life form never before seen on this world or any other…sentient twinkies…