A lot of variation among what each #browser offers in #privacymode - is it a bug or a feature? where would more interoperability help? where do we need to leave room for differentiation? @w3ctag is investigating the question github.com/w3ctag/design-rev…
I've been doing some research on #privacymode in browsers. (THREAD) Use cases: - To protect you from • the next person to use your browser • the network snooping • the site knowing too much about your prior browsing - For a fresh browsing context (no cookies/fingerprinting)

Jan 31, 2018 · 4:31 PM UTC

3
3
Replying to @w3cdevs @w3ctag
We need the ability to set this domain wide that doesn't change the gui. (2/2)
1
Does the Clear-Site-Data help a bit in that direction? It is more meant as a security than privacy feature, so it's probably not enough on its own (e.g. it probably still leaves traces in browsing history). cc @mikewest
1
Replying to @w3cdevs @w3ctag
I once did a site for Alternatives for Battered Women where we had a 'go away' button (took you to Google) for quickly leaving if the need arose. Had instructions on privacy modes, but push back arose from the gui giving away that they had private life on. (1/2)
Replying to @w3cdevs @w3ctag
@dontcallmedom Is this your fine work? It's fun (and surprising) to see that anyone is paying attention! :)
2
1