How do you feel about 418 being included in many legitimate http libraries?
Asklemmy
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
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
It's great: the Internet should have a bit of that sense of whimsy, and knowing that there's official support in many libraries for "you're asking me for coffee, but I'm a teapot" is one of those things that gets me through the day.
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.
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?
I always rather enjoyed the double entendre of "420 Enhance Your Calm", which was an unofficial response from Twitter's original API before "429 Too Many Requests" was standardized.
But I can't think of any codes which aren't already in there, that I'd use; there are a bunch that don't see much use, like "410 Gone", so the list could do with trimming down if anything.
What's your take on the fediverse frontier?
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.
You awaken my nostalgia, curiosity and sense of adventure when you say "explore the networks at the edge". Are there any other networks than lemmy / mastodon that you would suggest checking out?
Internet Relay Chat's been one of those things that's always felt out on the edge. I've been on EFnet since perhaps '03, and it's a lot quieter than it was...
With people moving en masse away from the centralized sites and their Firebase-implemented chats, we may see a pick up in traffic on the IRC networks, which would be good to see.
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?
I did go to a conference once where they were handing out laptop stickers, and in the pack was a 418 teapot.
Of course, a week after I stuck that to my machine, it died. Telling the laptop it was a teapot didn't agree with it, I guess.
What other such joke standards (by you or others) do you like?
A little lower down the stack, I always liked the Evil Bit in TCP, a standard which removes all need for firewalls heuristics by requiring malware or packets with evil intent to set the Evil Bit. The receiver can simply drop packets with the Evil Bit set, and thus be entirely safe forever from bad traffic.
At the physical interface layer where data meets real life, I especially enjoy IP over Avian Carrier; that link in particular is to the QoS definition which extends the original spec for carrying packets by carrier pigeon.
Someone tested the evil bit and found a selection of real-world networks that react to its presence
What was the inspiration for these internet standards?
That's actually the topic of the talk! Around 1995-96, HTTP was picking up all kinds of use outside the academic community, and people were tacking extensions on left and right; one of the biggest was file upload support, which was done by throwing HTTP and email into a room and having them fight it out. Which is how we ended up with the monstrosity that is "sending emails over HTTP", also known as "posting a form".
The author of HTCPCP decided to codify some of his concerns with these, partly as a joke; I noticed long afterward that his joke was only standardized for coffee, which Personally Offended me as a citizen of a tea-drinking nation.
Do you regret adding it, or with the knowledge you have today, would you still add the 418?
Since a bunch of languages have not implemented it, or/and has long discussions about it:
https://github.com/dotnet/runtime/issues/15650
https://github.com/golang/go/issues/21326
https://github.com/nodejs/node/issues/14644
https://github.com/psf/requests/issues/4238
https://github.com/aspnet/HttpAbstractions/issues/915
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.
How do you feel about people joking about and using 404 far off from HTTP?
Also: yay, AMAs have finally arrived. Whoβs gonna verify your identity, though?
The fact that otherwise non-technical people joke about staying in hotel room 404 just shows how pervasive the modern Internet has become. As an aside, it also shows the importance of a good error message; there are some errors (like "Not Found") in HTTP that are simple and clear, and some ("Bad Gateway"?) that are more impenetrable.
No-one jokes about staying in room 504, and the room service never arriving.
(And perhaps one of the larger Lemmies can get a hold of Victoria, get these AMAs going for real.)
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?
For Apr 1st RFCs in particular, the process is that you write your document in conformance to the RFC Editor's Style Guide and email it to the editor directly. If you have a not-a-joke standard that you'd like to be considered, that'll go through as an Internet Draft first, and then there are stages of review.
I haven't been through the latter, but the editors are very approachable over email; I had no issues submitting my RFC for review and revision.
Thank you for fixing a critical flaw in the original RFC.
What did you think about the Save 418 Movement? Were you involved in it in any way?
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.
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.
I need an ELI5 for this I'm a stupid Gen Z
You know sometimes you click on a link and it says "404 not found?" 404 is an HTTP status code. basically when you click on a website your browser makes an "HTTP request" to that website to get the web page, and it'll respond with a code to tell the status. 2xx is ideal, since it means OK. 4xx means it's an error on your end. (404, you requested a nonexistent link.) 5xx means it's a server error.
This person made 418, a status code for "I'm a teapot". It was intended as an april fools joke but it's used sometimes for when the server doesn't want to handle a request from the client.
Was it hard to get this standardized back in the good ol' days?
Do you think it would be as easy to do it now? If not, what challenges and hurdles would a RFC have to overcome?
The last thing I know that was pretty "significant" is the GNU Terry Pratchett header (https://en.m.wikipedia.org/wiki/Terry_Pratchett#Death) and that was a community effort.
There are joke RFCs almost every year, so it's not unprecedented to add to the standards. This year, one of the additions was a Death Flag to TCP, to indicate when a connection is about to terminate. The RFC Editors are very approachable when it comes to the Apr 1st RFCs: a "real" standard would need to be drafted by someone actually in the field, but the Apr 1st's are open to public submissions as long as you're willing to redraft/edit in accordance with the documentation standards.
It's worth noting that the Clacks header is an unofficial campaign, and hasn't been standardised; the 'Pedia states that some 84,000 sites return X-Clacks-Overhead, and my own is one.
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.
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.
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
The incident you mention is probably the most impactful, but there's also the time the Russian military blocked IPs outside Russia by returning 418 instead of the more logical 403.
What a fun AMA topic lol. I dont have a question, I'm just glad youre here, spreading the good gospel of your goofy internet standard
I don't have any questions but holy shit this is so cool.
What's the funniest legitimate non-joke standardization detail you've come across?
I enjoy that the original draft for the Referer header spelled it wrong, and now we're all stuck with the typo forever...
What's the process for submitting RFCs? And how do they pick which joke RFC they'll publish? That's a meeting I'd like to be a fly on the wall of