• 0 Posts
  • 13 Comments
Joined 2 months ago
cake
Cake day: August 5th, 2026

help-circle








  • That’s just because Brave tells websites that you’re using Chrome.

    All http requests include a “user agent” where the requester tells the server what agent the user is using. requesters can specify whatever they want - it’s not complex to tell the server you’re using tea leaves to render the server’s response.

    Some web pages are designed to tell the user that their browser is not compatible, if it doesn’t match a set of compatible browsers. So if you say you’re rendering the page with “tea leaves” it will tell you it’s not compatible because it doesn’t match “chrome” or “edge” or whatever.

    The outcome is - these alerts are rudimentary and not actually considering the capabilities of your browser.

    I generally use librewolf but as you say some pages are just broken, so I use ungoogled chromium for those pages.


  • Brave does this by randomization instead, which is far more effective.

    Randomisation isn’t necessarily more effective, it’s just a different strategy.

    Orion claims to this day that fingerprinting resistance is impossible, which is preposterous because Brave is doing it today.

    I think you mean Orion is saying RFP is ineffective, and whether Brave’s implementation is or is not is a question of semantics.

    Like most security measures, each decision is a trade off between security and usability. The Firefox / LibreWolf / TOR implementation is fine for most users:

    https://wiki.mozilla.org/Security/Fingerprinting#Terse_List