4 ms·
> At this time, 70% of the ad revenue is deposited into your in-situ wallet. Brave needs to know when and which ad has been shown to the user, to deposit that
by CrendKing 7y ago
> At this time, 70% of the ad revenue is deposited into your in-situ wallet.
Brave needs to know when and which ad has been shown to the user, to deposit that ad's revenue right? That means whenever an ad is shown "locally", it still needs to contact Brave server with user's identity behind of some encryption. Brave then shows the proof of ads being presented to users to ad provider to get revenue.
Sure, the user's interests are studied locally (and inefficiently because it runs on user's computer), but the result feeds back to Brave. How does that improve privacy?
At some point, Brave may either leak the data accidentally or decide to sell the data, because the data, which capture each uniquely identifiable user's interests, is valuable.
Or am I misunderstanding something here?
- sexisfun 7y agoHow do you purposefully leak data and get paid for it without a paper trail?
- BrendanEich 7y agoWe use a variant of privacy pass (Chaum blind signatures): https://github.com/brave-intl/challenge-bypass-ristretto https://github.com/brave-intl/challenge-bypass-ristretto The key is no user identifiable events and no ability to link events for a given user together. Advertisers want authentic aggregate results — they don’t want (at first or in bulk, also not legal in many places) user ids. We built an authentic but anonymous ad system.