Asklemmy

43946 readers

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

1138

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]

186 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] 81 points 1 year ago (5 children)

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.

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

Someone tested the evil bit and found a selection of real-world networks that react to its presence

[–] [email protected] 5 points 1 year ago

Fun read, thanks for the link!

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

With the advances on SDcards, IPoAC is getting better and better.

[–] [email protected] 27 points 1 year ago

As the saying goes, "for bandwidth, nothing beats a truck full of ~~tapes~~ 1TB MicroSDs hurtling down the highway".

[–] [email protected] 11 points 1 year ago* (last edited 1 year ago)

The Evil Bit sounds like the real Do Not Track header field

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

What's wild is that IPoAC was actually tested, and shown to have a higher throughput than the local ISP. Source

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

Relevant what if: https://what-if.xkcd.com/31/

[–] [email protected] 4 points 1 year ago

There really is an xkcd for everything....

[–] [email protected] 6 points 1 year ago

Wow. Never knew about these :)