3 ms·

"Brave has ads" is a good thing. Please, allow me to explain :) When you launch Firefox for the first time, you're already being setup and prepared to be serve

"Brave has ads" is a good thing. Please, allow me to explain :) When you launch Firefox for the first time, you're already being setup and prepared to be served to Google. Your data and more are being primed. The address bar serves as a key-logger, and your inputs (before ever explicitly navigating anywhere) are being sent to Google. Brave's ad notifications are opt-in; you have to turn them on. You decide their frequency. They're built on privacy. Users in a common region (e.g. United States) share a regional catalog. Your browser downloads a copy of this catalog, studies it locally, and decides when/if it should show any of the ads listed therein. When a Brave Ad is displayed, 70% of the revenue goes into a digital wallet. When you see an ad in Firefox, there's a good chance you just lost a little bit of your data, and received nothing in return. In Brave, these rewards stack up, and can be passively or actively distributed to the sites and properties you appreciate most online.

deleted 6y ago
[deleted]
0-_-0 6y ago
I have one remaining worry about Brave: If I choose to auto-contribute to sites, would it be possible to deanonymize me and derive what I look at from the BAT blockchain? E.g. if someone knows some of the sites I look at can they find out the rest?
- jonathansampson 6y ago
  These contributions aren't made on the public blockchain, so there is no way (not even for Brave) to know which site(s) you're supporting. Note also that (by default) the Brave Rewards wallet has no requirement for KYC. As such, there is no information about [you] connected to these transactions.
  - 0-_-0 6y ago
    Thank you for your answers in this thread. There's a lot of misinformation about Brave on HN.
TheCapeGreek 6y ago
While your arguments make sense, I find the continuous calling of other browsers as having keyloggers disingenuous. The only difference for Brave you've mentioned elsewhere in the thread is that it's opt-in by default instead of opt-out, which is fair. Also, by this logic any text field that does something with your input before explicitly pressing a submit button is also a keylogger. That just doesn't make sense.
- jonathansampson 6y ago
  When an application sends your keystrokes (or an accidental/unintended paste) off to a third-party without your consent, I think it is fair to call that a keylogger. > …by this logic any text field that does something with your input before explicitly pressing a submit button is also a keylogger. I respectfully disagree, since there are many things a text field can do with input which doesn't violate the user privacy (e.g. local spell-checking, input sanitization). My objection is with the automatic transmission of keystrokes to third-parties without the explicit consent of the user. Whether we agree to call this "key-logging" or not isn't as important. We can both agree that this could result in the unintended sharing of very sensitive data—that's the point I'm trying to make. Cheers!

deleted 6y ago

[deleted]

0-_-0 6y ago

I have one remaining worry about Brave: If I choose to auto-contribute to sites, would it be possible to deanonymize me and derive what I look at from the BAT blockchain? E.g. if someone knows some of the sites I look at can they find out the rest?

jonathansampson 6y ago
These contributions aren't made on the public blockchain, so there is no way (not even for Brave) to know which site(s) you're supporting. Note also that (by default) the Brave Rewards wallet has no requirement for KYC. As such, there is no information about [you] connected to these transactions.
- 0-_-0 6y ago
  Thank you for your answers in this thread. There's a lot of misinformation about Brave on HN.

TheCapeGreek 6y ago

While your arguments make sense, I find the continuous calling of other browsers as having keyloggers disingenuous. The only difference for Brave you've mentioned elsewhere in the thread is that it's opt-in by default instead of opt-out, which is fair. Also, by this logic any text field that does something with your input before explicitly pressing a submit button is also a keylogger. That just doesn't make sense.

jonathansampson 6y ago
When an application sends your keystrokes (or an accidental/unintended paste) off to a third-party without your consent, I think it is fair to call that a keylogger. > …by this logic any text field that does something with your input before explicitly pressing a submit button is also a keylogger. I respectfully disagree, since there are many things a text field can do with input which doesn't violate the user privacy (e.g. local spell-checking, input sanitization). My objection is with the automatic transmission of keystrokes to third-parties without the explicit consent of the user. Whether we agree to call this "key-logging" or not isn't as important. We can both agree that this could result in the unintended sharing of very sensitive data—that's the point I'm trying to make. Cheers!