Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
This is Firefox frontend to HaveIBeenPwnd.
Firefox 69.0 Released
21–30 of 331 posts
Re: Firefox 69.0 Released
#22I have a bunch of Facebook domains in my hosts, but for some reason Firefox 69.0 gets DNS from somewhere else and goes right through. Weird. The other stuff in hosts resolves correctly.
It could be DNS over https, which Mozilla have been experimenting with.
Re: Firefox 69.0 Released
#23I have a bunch of Facebook domains in my hosts, but for some reason Firefox 69.0 gets DNS from somewhere else and goes right through. Weird. The other stuff in hosts resolves correctly.
Is DNS-over-HTTPS on by default now?
Re: Firefox 69.0 Released
#24Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
It utilises K-anonymity, making it difficult if not impossible for this to become a massive data leak.
The email gets hashed on your device, and the start of that hash is sent off to the server. The server returns a list of all the hashes that might match. The client then checks that list for complete matches.
Re: Firefox 69.0 Released
#25> macOS users on dual-graphics-card machines (like MacBook Pro) will switch back to the low-power GPU more aggressively, saving battery life. macOS user base can now consider FF as a viable browser alternative.
Please be the case - this is reason #1 why I haven't switched.
Re: Firefox 69.0 Released
#26Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
Two things about that in reply to your comment:
1. Right now Firefox Monitor uses your Firefox account for signups. For somebody like me who already has a Firefox account, I don't see a net difference in risk here.
2. If you don't want to make one, then Monitor is transparent in that they just use https://haveibeenpwned.com under the hood (source: https://support.mozilla.org/en-US/kb/firefox-monitor-faq#w_h...), which doesn't require anything more than submitting your email and passing their Google captcha. It's unfortunate that they're not more forthcoming about this, but the option is there.
Re: Firefox 69.0 Released
#27nice
Re: Firefox 69.0 Released
#28I have a bunch of Facebook domains in my hosts, but for some reason Firefox 69.0 gets DNS from somewhere else and goes right through. Weird. The other stuff in hosts resolves correctly.
It could be DNS over https, which Mozilla have been experimenting with. https://support.mozilla.org/en-US/kb/firefox-dns-over-https
It wasn't on by default, but yeah, once I turned it on, it entirely bypassed hosts for everything, not just Facebook owned domains.
Re: Firefox 69.0 Released
#29> Firefox no longer loads userChrome.css or userContent.css by default improving start-up performance. Users who wish to customize Firefox by using these files can set the toolkit.legacyUserProfileCustomizations.stylesheets preference to true to restore this ability. How much of a performance improvement does this make?
Holy shit, just why? It makes virtually no difference. Neither applying CSS (they already use a lot) nor loading a file take any time.
Re: Firefox 69.0 Released
#30> Firefox no longer loads userChrome.css or userContent.css by default improving start-up performance. Users who wish to customize Firefox by using these files can set the toolkit.legacyUserProfileCustomizations.stylesheets preference to true to restore this ability. How much of a performance improvement does this make?
Last time I tried, I just couldn’t get userContent.css to work at all. Maybe a user error, but I’d really like an easy way to set some default styles to override the inane Web 0.5 era defaults such as zero margins and unlimited-width paragraphs. Reading Good Old HTML (tm) pages sucks, and although there’s the reading mode, it tends to simply drop vital content it doesn’t happen to support…