Comment by branon

3 years ago

On mobile (Android) it's different. You cannot continue past the warning in Firefox Daylight (or Chrome, of course).

about:config is also walled off in every mobile Firefox build except Nightly - and even then, the "safe browsing" keys toggle back every time the app restarts.

Android WebView listens to the safe browsing list too, so you can have native apps open up with blood-red warning screens which is very uncomfortable on mobile.

Don't think I've ever seen a GSB warning page that _wasn't_ a false-positive. Google also still links out to https://www.stopbadware.org/ on some of their GSB webpages, even though the site has been dead for ages.

It has the feel of a system staffed _exclusively_ by robots. This isn't necessarily a bad thing (Google does an overall good job) but it has its blind spots for sure.

Self-hosters getting sucker punched offline for a day or two isn't the worst (it happened to me just the other week). I get it, overall it's probably worth the collateral. I also get that mobile should _probably_ be protected more aggressively. But if you are on Android, I don't think there's any way to meaningfully disable it unless you are root.

It really pisses me off that even Firefox on desktop tries to scare you away from about:config with a lie, claiming that using it will void your warranty. Meanwhile the license under which Firefox is provided says "Covered Software is provided under this License on an "as is" basis, without warranty of any kind"

Firefox has no warranty to void. The warning message they make you view the first time you try to use about:config is simply lying to you. You might say "Oh well it's a well intentioned lie", but it's still a lie and there is no reason for this lie to even exist. The warning could be worded without this lie. It could simply say "You might break stuff if you continue" and that would be true enough and still scare off people who don't know what they're doing. So why the hell are they lying?