11–20 of 67 posts
Ugh, it has "disable webgl" because it's a "debatable" security concern? And disable ipv6? I hope people know what these settings are for before they apply these.
Retitle "Project to make Firefox suck more"
> Remove "(site) is now fullscreen" nag message and make it faster For a list that want to make the browser more secure, why do they want to remove the only line of defense against sites using fullscreen mode for phishing? > Disable PDF reader PDF.js has fewer security vulnerabilities than desktop PDF readers. > Disable 'safe browsing' aka. Google tracking/logging This seems like a really bad idea for most users
Not a great attempt IMO. The networking and UI things are a valiant effort. Mixing them with non-mainstream security concerns are a bad idea. You may feel that safe-browsing is tracking by the man, but advising newbies to turn it off is borderline irresponsible. Similar argument for ipv6 (wtf), error reporting (congrats: your bugs will never be fixed cause firefox doesn't know about them), and geolocation ("why doesn…
Made a PR: https://github.com/dfkt/firefox-tweaks/pull/1
This is an... opinionated list. Wish there was more annotation around what those opinions were.
> Remove "(site) is now fullscreen" nag message and make it faster For a list that want to make the browser more secure, why do they want to remove the only line of defense against sites using fullscreen mode for phishing? > Disable PDF reader PDF.js has fewer security vulnerabilities than desktop PDF readers. > Disable 'safe browsing' aka. Google tracking/logging This seems like a really bad idea for most users
The only time I ever see the fullscreen message is when the screen has essentially already fullscreened itself in a case where I want it to. =/
Why Reading mode is even considered "bloatware"?
I'm not the biggest fan of hello in firefox, but I've gotten some light mileage out of it, so I guess I can't be too upset. Pocket though just really shouldn't be in the browser.
Not a great attempt IMO. The networking and UI things are a valiant effort. Mixing them with non-mainstream security concerns are a bad idea. You may feel that safe-browsing is tracking by the man, but advising newbies to turn it off is borderline irresponsible. Similar argument for ipv6 (wtf), error reporting (congrats: your bugs will never be fixed cause firefox doesn't know about them), and geolocation ("why doesn…
It's not so bad. You can sort prefs by user-defined, they're in bold, and each one has a reset-to-default option.
Also you can do a whole browser reset which preserves only passwords/bookmarks. Instructions: https://support.mozilla.org/en-US/kb/refresh-firefox-reset-a...
And firefox profiles might be handy for this too (from the command line add --ProfileManager or -P ).
> Remove "(site) is now fullscreen" nag message and make it faster For a list that want to make the browser more secure, why do they want to remove the only line of defense against sites using fullscreen mode for phishing? > Disable PDF reader PDF.js has fewer security vulnerabilities than desktop PDF readers. > Disable 'safe browsing' aka. Google tracking/logging This seems like a really bad idea for most users
That's probably because there is one PDF.js and dozens of desktop PDF readers.
PDF.js sprouts CVEs at an alarming rate. It should be disabled until someone does a full-program security audit.
> Remove "(site) is now fullscreen" nag message and make it faster For a list that want to make the browser more secure, why do they want to remove the only line of defense against sites using fullscreen mode for phishing? > Disable PDF reader PDF.js has fewer security vulnerabilities than desktop PDF readers. > Disable 'safe browsing' aka. Google tracking/logging This seems like a really bad idea for most users
The only time I ever see the fullscreen message is when the screen has essentially already fullscreened itself in a case where I want it to. =/