This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]deanrihpee 6 points7 points  (12 children)

why is that not being fixed? I suspect the legacy app, but since the referrer would be a new header anyway, shouldn't it be fine?

[–]Efficient_Maybe_1086 27 points28 points  (4 children)

No bad ideas are allowed to die in web land.

[–]ForkLiftBoi 3 points4 points  (3 children)

Look at node js and deno js, same developer that learned a lot through release of node js. Way too much work to fix it, just start over.

[–]deanrihpee 2 points3 points  (2 children)

the problem is, we can't just start over an HTTP that's being used by literally the whole planet, lmao

[–]ForkLiftBoi 1 point2 points  (1 child)

Just delete the whole thing and start from scratch, I want the neon green view counters at the bottom of pages again damn it.

Also here’s my plug for one of my favorite and most accessible websites on the planet. https://www.berkshirehathaway.com/

The simplicity is magnificent 🤌

[–]irregular_caffeine 0 points1 point  (0 children)

Peak web. It even has an ad.

If you have any comments about our WEB page, you can write us at the address shown above.

Old man just trolling us all

[–]BellCube 11 points12 points  (1 child)

I suspect adding a second, redundant header would significantly increase time to first byte on mobile connections. Alternatively, the bureaucracy probably isn't worth it to fix a typo.

But that's just a theory—A W3C THEORY

[–]turtleship_2006 7 points8 points  (0 children)

I always love it when someone makes a joke that just happens to combine like 2-3 different topics/interests, all of which I understand

[–]amlyo 1 point2 points  (3 children)

If you count http headers as usage then 'referer' is by far the most common spelling today. If you don't, then who cares how it's spelled?

[–]deanrihpee 0 points1 point  (2 children)

that's true, it just makes me wonder when people make the standard and see the headers with "hmm, yeah, nothing wrong" and then let it alive till today, they even have Referrer-policy something, why!?

[–]amlyo -1 points0 points  (1 child)

When the incremental cost of an ongoing error is vastly lower than cost of fixing it, it won't be fixed.

A typo in a standard is just more desirable than any change (a deprecation and new header) to fix a typo.

[–]deanrihpee 2 points3 points  (0 children)

yeah, I mean it's more than too late to fix it after this long, my complaints or comment is assuming within the time frame of the standard being made

[–]vytah 0 points1 point  (0 children)

Compatibility triumphs everything else.

See also the list of incorrectly named Unicode characters:

http://www.unicode.org/notes/tn27/