So the ads you see are just based on country, type of device (windows,linux,macos,android or ios), and your search term, which is the minimum you really need for relevance. But these are not kept in any sort of tracking profile and Brave doesn't know anything about you, or queries across sessions. And unlike most of the search engines out there right now, we are motivated to ensure that the ads do not become a mess that buries organic results.
Hi blitzar, I'd like to clarify a few points here. First, meet.jit.si is a free development/experimental version of the Jitsi software that powers the paid 8x8 Meet product. From our discussions with the 8x8 team this is where they pilot new and potentially unstable features over weeks or months before they deploy it on their paid infrastructure. Per the privacy policy here https://jitsi.org/meet-jit-si-privacy/, they mention: "To provide the meet.jit.si service, 8×8 processes network and usage information.." That data is of course used to improve the service before deploying to the more stable versions.
Brave Talk, both free and premium, is powered by the stable/production 8x8 infrastructure, that has been vetted, usually for weeks before. Brave intends to run this as a fully reliable service that our users can count on.
Update, I checked with the 8x8 team, and it will warn from 21 to 25 users, and then disable when the 25th user joins. You'll see the green video bridge encryption notification turn off at the top at that point.
Once the moderator enables "Video Bridge Encryption" it is automatically enabled for other participants. I believe that if a 21st user tried to join it would error out, but let me confirm this with the 8x8 team.
Hi I'd like to correct this, if you have enabled "Video Bridge Encryption" in Brave Talk, this is not the case. Calls of up to 20 participants would be encrypted, using keys locally exchanged among participants. The SFU wouldn't be able to decrypt these video/audio streams. Of course, as would be standard and expected, the SFU would decrypt the transport layer of encryption, but wouldn't be able to decrypt the second layer of video/audio encryption. You can find more about the current underlying Jitsi encryption implementation here: https://jitsi.org/wp-content/uploads/2021/08/jitsi-e2ee-1.0....