Asklemmy

44151 readers

1820 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

1209

I'm the author of an April Fool's Internet Standard, AMA (self.asklemmy)

submitted 2 years ago by Two9A to c/[email protected]

183 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 33 points 2 years ago (1 children)

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.

[–] Two9A 37 points 2 years ago (1 children)

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.

[–] [email protected] 17 points 2 years ago (1 children)

Getting more likely with each passing year.

[–] [email protected] 8 points 2 years ago (1 children)

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.

[–] [email protected] 6 points 2 years 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...