I finally saw me nudged to install another add-on in Firefox to “fix” the #referrer header. Bad enough that #YouTube requires a referrer header to allow #embed|s. Now I also fell over OSM requiring one (this one I can get). But I don’t want to globally enable cross-origin referrer headers. Hence “Toggle Referrer.” It disables refererrs by default, and has a small spoofing list for annoying web resources that really want to have a referrer. YouTube gets a Google.com referrer. Take that, big tech!

https://addons.mozilla.org/firefox/addon/togglereferrer/

https://blog.gslin.org/archives/2026/03/22/12949/%e6%8a%8a-plausible-%e6%9e%b6%e8%b5%b7%e4%be%86%e7%8e%a9-ga-%e6%9b%bf%e4%bb%a3%e5%93%81%ef%bc%9f/

把 Plausible 架起來玩 (GA 替代品？)

#ai #analytics #blog #bot #plausible #referer #referrer #spam #wiki

https://blog.gslin.org/archives/2025/12/26/12821/%e9%98%b2%e6%ad%a2-csrf-%e7%9a%84-sec-fetch-%e6%96%b9%e6%a1%88/

防止 CSRF 的 Sec-Fetch-* 方案

#apple #browser #cross #csrf #forgery #form #header #hidden #http #ios #iphone #referer #referrer #request #safari #SecFetchSite #security #site #token #value

Chromium 136 freaked up CSS with a strange privacy feature and broke a:visited links.

Display with CSS of visited links fail if no referrer is sent.

I could not find any hint from Chromium Devs and no changelogs why Chromium 134 needed no referrer whereas Chromium 136 needs referrer!

Bug?

#Chromium #CSS #Referrer #WebServer #HTTP #WebStandards #Usability #Webdev

The no 1 word I bet you as a #webdev always wrote wrong though having used it likely hunderd times.

It's a header.
The referer header. Yes, #referer[sic], not the correctly spelled version #referrer.

Don't believe me? Look in your browser.