Warning to all Brave Browser Users
Blocking variations.brave.com which is used for A/B testing could potentially break Brave’s functionalities. For me did Brave’s “forgetful browsing” feature broke which seems to be disabled by default if you block this domain.
Firefox is safer and tbh, has probably the best UX and aesthetics out of anyone. Brave is garbage.
safer?
Brave is just a shill for Google mothership. Firefox is leading privacy and security through browsers.
Firefox has a weaker sandbox than chromium and less mature site isolation and therefore has lower security. privacy is a different story, but remember you’re only as private as you are secure so Firefox is inherently not that private assuming a malicious site escapes the sandbox.
I’m fully against chrome’s growing monopoly as well as Google surveillance capitalism but let’s not be so dramatic with the “google mother ship” nonsense.
using chromium as a base does not equal data being sent back to Google, just like using Android as a base doesn’t inherently send data back to Google.
Source: madaidan
Anything you say is as informative and coherent as a baby’s babble, if you believe him or any of the closed source shilling “security zealots” in FOSS community.
As a Firefox user, the only thing Brave does that I wish Firefox would copy is their fingerprinting resistance. I know Firefox does have fingerprinting resistance but it’s nowhere near the same level as Brave.
No. Firefox with RFP, Arkenfox user.js, Librewolf or Tor-Browser unifies your fingerprint. Its universal among users. Brave scrambles it, while some may say that is actually not a real fingerprint and can be detected, making you stand out extremely
Just to be clear, are you saying Firefox with fingerprinting resistance used in conjunction with Arkenfox user.js provides fingerprint unification, similar to what Tor browser does? I’ll have to check that out.
I think both approaches are valid tbh. Having a unique fingerprint obviously uniquely identified you, but if it’s randomised then your browsing sessions can’t (in theory) be linked.
The Chameleon extension could solve some of the fingerprinting issues as it can randomize the browser and OS info that is sent.