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!

  • boonhet@lemm.ee
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 year ago

    I have no questions, but I want to let people here know that there are two excellent websites related to this: http.cat and http.dog, for looking up HTTP status codes.

    For an example, if http.cat/418 doesn’t brighten your day, I don’t think there’s much that can.

  • Erk@cdda.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I had been an advocate of getting just an ordinary person to do the first Lemmy ama but apparently we’ve got an absolute legend.

    Have you ever had a favourite reference to your joke come up?

  • Veraticus@lib.lgbt
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Congratulations on creating such a cool piece of Internet arcana!

    What do you think the silliest/most useless response status code is aside from 418?

    Were there any codes you wish had been included that haven’t been for some reason?

  • binwiederhier@discuss.ntfy.sh
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Thank you for contributing to the magic of the old school internet.

    My question: How does one get to write an RFC? Do you have to become part of a certain group, or just be known in certain circles, or do you just start writing and then submit it somewhere? If I had a great idea that I think should become an RFC, what is the process to make this a reality?

  • Rikudou_Sage@lemmings.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Not a question, but we use 418 in production! We have a nginx router that routes pages based on its path to either old frontend or new frontend. I wanted some easy way to handle the routing (and to not repeat myself), so I set the new frontend as a handler for 418 error and then just return 418 in the nginx for any page I want on new UI. I chose 418 because the others could be actually used by the old frontend and it could get all weird.

  • Fenzik@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    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

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

    I am interested in writing a real RFC, what kind of mailing list etc should I join in order to make my RFC real?

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

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

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

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