Conversation

This Tweet was deleted by the Tweet author. Learn more
Quote Tweet
Brave has always been a sketchy browser reeking of desperation. I've taken issue with their usage of DRM, their decision to have a hard dependency on Play Services and their sketchy cryptocurrency activities including their very likely illegal ICO launch. twitter.com/DanielMicay/st
Show this thread
This Tweet was deleted by the Tweet author. Learn more
Brave (as in the browser) is open source. All of the sketchy stuff they've included has been open source and available for people to look into it. They have various services that are likely proprietary and the cryptocurrency they control but the browser itself isn't proprietary.
1
1
twitter.com/DanielMicay/st is an important part of that thread. Brave has done a substantial amount of useful work on Chromium. Unfortunately, you get it together with some problematic changes and some sketchy behavior. Mostly good developers but problematic leadership above them.
Quote Tweet
Unfortunate there's useful privacy work caught up in it. Don't bother feeling bad for them over the overreaction and misrepresentation of the affiliate id stuff. They pull this all the time. Look at the Scroll To Text Fragment news cycle. This is a taste of their own medicine.
Show this thread
1
1
I'll consider deleting that thread and other threads about Brave because I'm not interested in conflict with them or their supporters. I think it's unfortunate that so much of the good privacy work on Chromium is tied up in a problematic project without much hope of upstreaming.
1
1
It would be nice if all the projects basing browsers on Chromium would stop using incompatible licensing and start working together. Chromium should be run in the interests of all the browsers using it rather than being almost entirely focused on Chrome and controlled by them.
1
1
If they aren't willing to do that for Chromium yet as Apple did with LLVM, then the projects building on it should be working together to have a very well maintained set of high quality shared patches under the permissive Chromium licensing to share them and get them upstream.
1
1
This Tweet was deleted by the Tweet author. Learn more
We use the MIT license or the Chromium licensing for our own work on it in Vanadium. We'd be fine with anything licensed as MIT, BSD, Apache, etc. We care a lot about the code being correct, clean and maintainable which are common issues with downstream changes from elsewhere.
1
1
Show replies