I'm the author of an April Fool's Internet Standard, AMA

Two9A@lemmy.world to Asklemmy@lemmy.ml – 794 points –

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!

182

You are viewing a single comment
View all commentsShow the parent comment

There are far more robust methods of fingerprinting to spy on users anyway (adding up all the details of screen size, available fonts, language, os, etc, etc), so I don't think removing the user agent would have much impact in reducing fingerprinting alone. It's also useful as a quick and simple way to check the type of device, os, or browser the user is on and serve the correct content (download link for one's OS) or block troublesome clients (broken bots)

(adding up all the details of screen size, available fonts, language, os, etc, etc),

not if you just simply turn off javascript.

I bet you can detect window size with css media queries and invisible “background-url” values for rendered items.

I don’t know if “display: none” prevents loading of background-url targets though.

Then browsers should just download ALL background-url images beforehand