Asklemmy

43822 readers

1228 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]

1130

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

submitted 1 year ago by [email protected] to c/[email protected]

188 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] 26 points 1 year ago (1 children)

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

[–] [email protected] 46 points 1 year ago (2 children)

I enjoy that the original draft for the Referer header spelled it wrong, and now we're all stuck with the typo forever...

[–] [email protected] 23 points 1 year ago* (last edited 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.

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