I don't trust their promises.
I don't trust their promises.
I guess there's the loss in privacy where it's known what browser I use, but that's not the kind of privacy loss that worries me.
They've got to pay the bills somehow, and while they should have been more up-front about doing it this way, and it is a breach of trust, it still landed in the realm of "reasonable asking for forgiveness" to me.
> I don't trust their promises.
Maybe I'm just not seeing which promise it was that was broken so badly.
The unspoken promise that web browsers should be impartial user agents that render the content as its authors intended, rather than man-in-the-middle agents that modify the content as they see fit.
The fact this change also benefitted Brave authors directly is an additional breach of trust.
Inexcusable in my opinion, and with the other shady cryptocurrency dealings mentioned in a sibling comment, it's enough for me to never want to use their browser or anything associated with them.
I appreciate they're trying to change the status quo of how the web works and is monetized today, but they started on the wrong foot and their reputation is forever tarnished in my eyes.
- It monetises the content created by other people. As someone who lives off the content I create, I'd take offence to that, particularly if it changes already monetised links.
That's incorrect. Brave added a feature to the browser which would list Affiliate Links, if any, in pre-search UI. As the user typed something into the address-bar (e.g. 'Bitcoin'), Brave (the browser) would check local data to see if there were any relevant affiliate links. If it found one, it would enumerate it among the other search suggestions in the address-bar dropdown.
Note, affiliate links were not inserted into pages. Links on pages were not modified. Requests en-route were not re-routed. There were many ways people described this feature; most of them were incorrect. So what was the problem?
Our implementation of this feature had a mistake; it matched against fully-qualified URLs. As such, if you typed 'binance.us' into your address bar, and Brave had an affiliate code for that domain (which would be visibly shown before the user navigates), the browser sent you to the affiliate link instead of the non-affiliate link.
When this issue was brought to our attention, we confirmed the (undesired) behavior, owned the mistake, fixed the issue, and confirmed that no revenue would be made from that affiliate link. Mistakes do happen in software, and they will happen with Brave (try as we might to avoid them). What's important is that we moved quickly, fixed the issue, and maintained transparency.
Traffic attribution is not uncommon in browsers though; open Firefox and type something in your address bar. When you hit Enter, you'll find that Firefox adds a traffic-attribution token to the URL too (although they do this only after the request is being issued; Brave showed the token before navigation).
I hope this helps provide a bit of context to a very misunderstood bug in Brave's past.
And contrary to upthread, we never "replaced links in web pages".
Also, when people got upset, Brave changed it too. It's not like they promised to never make money. I don't see that as a reason to trust Brave any less. It seems like a good influence on the web.
I am using Firefox and I trust Mozilla more than I trust Bravo.
See the Tom Scott and BAT incident. Kinda shady how it was handled.
Just a few weeks ago he went on an anti-Fauci and anti-mask conspiracy rant in the thread about him appearing on Lex Fridman's podcast, when nobody was even discussing politics.
Your second paragraph is easily disproven. I didn't bring up Fauci, someone else did to derail the discussion about my conversation with Lex:
https://news.ycombinator.com/item?id=26133207
That derailing comment is flagged and now dead.
I've flagged your comment here, it is either dishonest or else just sloppily malicious in the wishful thinking mode with which you led in the first sentence.