I used to be optimistic about Brave, but I no longer consider it to be a good project. It has had some serious issues with security and the intent behind it is starting to seem nefarious. Monetizing other people's content was always sketchy and their DRM is going far beyond EME.
Conversation
Replying to
Firefox has serious security issues, and I don't recommend using it. The sandbox is far weaker than Chromium and it doesn't provide site isolation which is a necessity in 2019. On Android, Firefox doesn't provide a browser sandbox at all, which is just completely unacceptable.
1
1
8
Replying to
Brave is a better choice than Firefox. I'm not saying that Brave is a bad choice as a browser in technical terms but that the project has the wrong motivation behind it. It's at odds with privacy and it's now clear they value the attention nonsense more than they do privacy.
1
1
4
Replying to
I largely feel the same way about Mozilla's approach with Firefox. Apple seems far more interested than Mozilla in delivering actual privacy rather than the appearance of it, although Apple recently started using it as part of their branding / marketing which is what taints this.
Replying to
I don't really have a browser recommendation right now. I liked that Brave took the solid Chromium base and seemed to be on the path towards turning it into a privacy-focused browser but it's clear to me now focus is elsewhere and privacy isn't going to win when they conflict.
1
5
Show replies
Replying to
Apple has much more leverage to force breaking features onto websites because there are no alternatives to using WebKit on their platform.
This affects rollout of privacy features on Apple vs non-Apple platforms.
1
Replying to
I'm also talking about support for Content Blockers which are a privacy-friendly way to support declarative content filtering rather than having extensions given free reign over traffic. For webRequest, the API is also not robust, and doesn't handle edge cases / failures well.
1
Show replies