Our user base has grown by more than 10x these past years, recently passing 32 million monthly active users, and if you add the increasing number of platforms, channels, and architectures to the mix, then our build and release capacity had to scale 100x.
We propose a new privacy-first framework to solve recommendation by integrating federated learning with differential privacy. This work on private federated recommendation is only one example of how we intend to leverage federated learning with privacy on the Brave browser in the future.
We received 10 RFC&C proposals from teams focusing on both L1 and L2 tech that brought practical insights on how to improve the original THEMISv2 protocol spec. In this blogpost, we’ll dive into each of the received proposals and provide pointers for the material each team submitted for the RFC&C.
The THEMIS RFC&C event, which started early February, has brought independent researchers and over 10 companies together with the Brave research team to comment and propose directions for the future of the Brave Ads protocol.
A month ago we announced an RFC&C for the THEMIS protocol which is meant to progressively decentralize the Brave/BAT Ads infrastructure, while providing users and advertisers with the ability to verify that the protocol is properly computing user rewards.
Brave is a company where privacy isn’t just a feature; it’s a requirement. This is perhaps most obvious in the Brave Browser, where we block trackers, prevent fingerprinting, and include a privacy-preserving, opt-in and user-first ad-system, but Brave’s focus on privacy goes far beyond the browser.
We’re using Brave’s new private CDN to fetch RSS feeds anonymously and the browser’s personalization capabilities to rank headlines with a simple algorithm that will make the experience interesting for everyone.