Posted on 10/23/2017 3:03:26 PM PDT by CedarDave
Bkmrk.
.
Same here. Now I can't get to my logins and passwords without going to Safe Mode and a couple of my popular add-ons are not working either. While investigating the latter problem, I came across these articles on how Firefox was going to bomb its own browser in a couple of weeks.
I must have a strange way of looking at things:
Good enough is good enough
I use 10-12 add-ons. About half have already said their product will die, as they no longer intend to update them.
Some of the ‘new’ ones are quirky and take getting used to.
Okay but what is it? Like FF?
I have plenty of other issues with Brave.
I tried Brave. It was okay, but few options to customize.
Then, they upgraded and changed the GUI to crap. I deleted it.
My gosh, all these browser problems, lol.
So, which browser do my fellow FReepers recommend for privacy, speed, results, etc?? :-)
It's based off the same open source as FF but superior in every way. It loads and runs much more quickly, the memory bloat is much less, and it still supports all your favorite add-ons. (For me, NoScript and Fluff Busting Purity are essential.) Menus and functionality are almost exactly the same as FF, so there is no dramatic learning curve.
Use Waterfox (see my other posts on this thread). So far, it has installed and allows me to use my favorite add-ons. Give it a try.
However, it acts in coordination with a system of DNS servers all over the world which misidentify your IP address, making it impossible to know who/where you are.
The problem is, the "onion routing" scheme is hackable by man-in-the-middle impersonations. If as few as about a half dozen of the volunteers providing service are compromised (and they probably have been) your location and history will be known to the man-in-the-middle, so it's likely that the TOR network is thoroughly infiltrated by state actors. No one knows for sure.
Its origins are also murky; it's possible (likely?) that the routing system was created by US national intelligence; the concept behind it certainly was.
Firefox is becoming a dog. I have Linux Mint and see Firefox memory footprint routinely exceed 1.5 gigabits. It also has problems grocking javascript.
Thanks for the links.
I have noticed that on some pages, I get a “this page needs you to download Adobe Flash Player...” I already have it but it seems FF does not support it.
tech ping
Remember the browser wars of the mid 1990s that involved Microsoft Explore and Netscape Navigator? Those were trying times for all of us. This was when Cascading Style Sheets exploded upon the scene and wreaked havoc on all.
Well the browser wars of 2018 promise to be positively deadly and barbaric. May the best browser win and have mercy upon the vanquished.
So something to stay away from I guess. I’ve been using FF for quite some time and I don’t like IE, I’ve tried to use it and I don’t like it.
IMNdi commented Sep 28, 2017:
@watchpocket If I may chime in, Waterfox is a one man project that proposes to maintain pace with Mozilla (it did) and (now) keep addon compatibility. That is a monumental task and doesn't solve other Mozilla issues, like the control they took away from the user or future decisions to kill the UI and user privacy. Mozilla announced a new-new UI.
It is not in the scope of Waterfox nor is it feasible for a person to maintain a "freeze" of features. Waterfox is essentially a stripdown of Firefox that proposes to (now) maintain XUL after Firefox drops it. This would be the first major workload spike on the maintainer.
By contrast, PM is a standalone browser and while new features are uncertain, stability is not. PM never gained the new Australis so there is nothing to maintain.
This is what kept me from going Waterfox and put the effort into PM.
Also, PM is faster, since it never got the later bloat. Whether you think that is good is what your definition of bloat is. I happen to think Firefox has been gaining weight recently.
~~snip~~
mgol commented Sep 28, 2017:
@IMNdi I share your concerns about Waterfox. I've been watching recent changes to Firefox and there's been a massive number of commits stripping out code needed only for the XUL add-ons infrastructure to work, legacy code not yet removed due to compatibility concerns with add-ons etc. It's going to be very hard to revert all those changes and at the same time keep the code up to date with Mozilla latest changes. It's not as simple as it was with restoring NPAPI compatibility.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.