Safe to say, this proposal has gone down like a poweroff -fn
“Phone calls home”
In previous versions you could search your about:config on the “value” field, this is no longer possible. Searching for https:// and http:// would give you a list of numerous URLs, most of which are under Mozilla’s own domains. Some might argue that things like updates are necessary to ensure a secure browser. Others might argue that they have run very outdated browsers without problems for years, and that combined with forced updates and the Maintenance Service, the log files generated produce a not-insignificant amount of information about users.
Suggesting using an decades old and known exploitable browser because “well I never got hacked” is like saying vaccines are unnecessary because “well I never got sick”
@bamboo
Feel free to point out where anyone suggested that anyone else should use “an decades old and known exploitable browser”.
For the sake of being complete, I downloaded Firefox v2.0.20, which of course does not come in x64 flavour. So after installing assorted i386 libs, it did in fact run. The first-start popped up the image below, after which it showed a clearly broken and distorted mozilla.org page. It was also essentially unusable, since it doesn’t meet the minimum TLS requirements to view most sites. Disroot SearX, ddg.gg, StartPage, ecosia.org, and even the client test page at ssllabs.com all failed to load. google.com did load, but searching for “alternative search engines” was a failure because none of the sites in the results could be opened. Now did you really think that me saying v2.0.20 is the last “good version”, meant that anyone should rush off to download it and try to use it today?
Warning: Do not stop blade with hand.
