andersju

Plenty of terminal-based options (e.g. Lynx) for Gopher.

Gopher pretty much died long before Google was a thing. Here's a good article: https://www.minnpost.com/business/2016/08/rise-and-fall-goph... (lots of interesting comments below the article from many of the people involved)

Yeah, I have to update that part. This works in Edge (as well as FF, Chrome, Safari) to kill referrers completely:

  <meta name="referrer" content="never">

Should also note that it's possible to have fallback values (https://www.w3.org/TR/referrer-policy/#unknown-policy-values).

For sure, it's just hard to tell them apart from a technical point of view. Tracking Preference Expression (DNT) [0] does make it possible with a Tracking Status Resource's same-party property [1], but it seems like almost nobody uses (or talks about) this. Medium.com is the only major site where I've seen it implemented: https://medium.com/.well-known/dnt/

[0] https://www.w3.org/TR/tracking-dnt/

[1] https://www.w3.org/TR/tracking-dnt/#rep.same-party

Hey, I'm the main author of this. Happy to see that people like it!

As I wrote elsewhere in the comments we're planning to redesign the results page and rewrite all the text later this year. The current page hasn't changed much since mid-2016. Need to refresh/expand technical advice, be more clear about the limitations of the service, etc. I'll note down all suggestions here.

I'd also like recommend a similar project that was inspired by Webbkoll: https://privacyscore.org/ -- it's slower, but also integrates things like testssl.sh, and most importantly lets you make lists of URLs to check. It uses OpenWPM [0] which has been used for many interesting studies,[1] such as "Online Tracking: A 1-million-site Measurement and Analysis".[2] (Webbkoll uses Phoenix+Puppeteer)

[0] https://github.com/citp/OpenWPM

[1] https://webtransparency.cs.princeton.edu/webcensus/index.htm...

[2] http://senglehardt.com/papers/ccs16_online_tracking.pdf

Definitely. Planning to redesign and rewrite the whole results page later this year.

Just a historical note that I found interesting - it was in fact obvious (to some) already 22 years ago. From RFC 1945 (HTTP/1.0), May 1996, 10.13 Referer [sic]:

"Note: Because the source of a link may be private information or may reveal an otherwise private information source, it is strongly recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From information."

(https://tools.ietf.org/html/rfc1945#section-10.13)

This recommendation was not followed in any meaningful way, but Referrer Policy (https://www.w3.org/TR/referrer-policy/), which supports a whole bunch of different policies and is very easy to implement (and now widely supported), at least makes things slightly better.

Indeed. I'll change "Input URL" to "Checked URL" or something like that.

Looks like you missed the : in http://. I'll remove the http:// from the placeholder, though, as it's not actually necessary.

Noted, thanks! I'm planning to redesign the whole thing in a couple of months. I'll definitely keep that in mind. /author

Yup. It's the untouched gif he sent me.

Seeing the interest this generated, I'm working on a follow-up :)

Unfortunately this is not just a UK thing. Every EU country is forced to do this.

A similar law was passed in Sweden just the other week and will come into effect on July 1, despite heavy criticism from pretty much everyone.

So how could they pass such a law? It's from an EU directive, more specifically 2009/136/EC [1]. A directive is something that every member state is _required_ to implement into national law, whether they like it or not. AFAIK every member state is supposed to have implemented this by now. Sigh.

[1] http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2...