Conversation

This Tweet was deleted by the Tweet author. Learn more

Thibault

#StandWithUkraine

@thibaultmol

Jun 3

The fck are you even on about.... I don't trust brave - proprietary - did weird thing by replacing referral links on websites androidpolice.com/2020/06/07/bra - these letters - promotes weird crypto shit

androidpolice.com

Brave Browser caught adding its own referral codes to some cryptocurrency trading sites

No, Brave is not a privacy browser

Replying to

and

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.

Replying to

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

Daniel Micay

@DanielMicay

Jun 8, 2020

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

Replying to

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.

Replying to

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.

Replying to

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.

Replying to

We've collaborated with Bromite a lot but unfortunately they felt they had to start licensing their code as GPLv3 to deter people taking advantage of them as much, which has made it so we can't include their code anymore since we stick to permissive licensing we can upstream.

This Tweet was deleted by the Tweet author. Learn more

Daniel Micay

@DanielMicay

Jun 4

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.

Replying to

It's unfortunate that many of the projects are using more restrictive copyleft licensing because that means the changes can't be submitted upstream and projects with permissive licensing can't use them. We're finding it frustrating they use our changes but we can't use theirs.

7:53 AM · Jun 4, 2022Twitter Web App

Replying to

It doesn't mean we'll use copyleft licensing though. Our users just won't have useful features they could have if the code was permissively licensed. We care a lot about all our changes to existing projects being very clean patch sets which could be submitted upstream any time.

Replying to

We see it as really important to upstream as much as possible so we can move on to other things. Most of the work on Vanadium is porting forward the changes and maintaining them. This has blocked us adding certain major features because the code isn't yet clean enough, etc.