Obscurity through privacy:
If you're on @FirefoxNightly and you're having frustrating and bizarre timezone issues...
...maybe it's because you set privacy.resistFingerprinting = true.
This explains so much weird stuff over the last couple of weeks.
-
Show this thread
-
Also: If your window sizes were not being restored correctly after a restart. It's like the browser has ghosts.
3 replies 0 retweets 1 likeShow this thread -
Replying to @dietrich @FirefoxNightly
I remember filling that as an issue maybe a year ago? It also makes your http://Date.now () all wrong, which has hilarious consequences for things like Gmail.
1 reply 0 retweets 1 like -
Replying to @TheRealPomax @FirefoxNightly
SO much weird stuff! Do you have a bug #?
1 reply 0 retweets 0 likes -
Replying to @dietrich @FirefoxNightly
Bugs: 1419656 (implicitly), 1420234->1364261 (date). I requested making things more fine grained, so that you could say p.r.=true but also add p.r.excludeTimeStamps=true, p.r.excludeSizing=true, etc. which was shot down, and I don't understand. I still back that idea.
1 reply 0 retweets 0 likes -
(if you're offering power users a way to turn off fingerprinting, the argument 'disabling parts of it would allow fingerprinting' is literally what a power user would expect. Limiting the surface rather than removing it entirely is fine to someone who wants full control)
1 reply 0 retweets 0 likes -
Replying to @TheRealPomax @FirefoxNightly
Thanks! Hmmm, we can't realistically ship anti-fingerprinting without the user fully understanding the impact.
1 reply 0 retweets 0 likes -
Replying to @dietrich @FirefoxNightly
But that's the thing: which user? If this is turned on by default for regular users, that's a really bad plan because it turns off things that users should have reasonable expectation don't break. Like http://Date.now (), the canvas element's API working, etc. etc.
1 reply 0 retweets 0 likes -
So if we want this on by default, we need an MDN article with the exhausting list of which behaviours are changed - but if we have that, then that immediately makes it almost trivial to note which exception flag to use for each of those, so users can make informed decisions.
1 reply 0 retweets 0 likes -
And probably a UI indicator that shows the current page not rendering as intended due to privacy restrictions, with the standard expanded window showing which things resistFingerprinting block(s/ed) for this page specifically, and toggles so the user can say "allow THIS thing"
1 reply 0 retweets 0 likes
Yeah, this is what I'm thinking - a visual indicator should be required to ship, whether default or not. Not sure it'd ever be turned on by default because of all the behavior changes.
-
-
Replying to @dietrich @FirefoxNightly
My idea was something like this, where it's super obvious FF is (intentionally) "breaking" pages, with UI that lets you inspect how it's doing that and simple toggles to override individual ways "on this page"/"in general".pic.twitter.com/Rql5v7Wszn
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.