News for hackers. Stuff that matters.
Re:Wikipedia Is Now a Brave Verified Publisher by zargon on Thursday August 29, 2019 @11:55AM (#20830621)
I really like what Brave is doing. I wish it was built on Firefox instead of Chromium. I just don't see myself leaving Firefox without major upheaval in the browser space.
Re:Wikipedia Is Now a Brave Verified Publisher by onyva on Thursday August 29, 2019 @03:21PM (#20832711)
Mozilla's focus is user's rights online and privacy. They have a track record doing that. Brave (AKA AdBuddy) is just another product, desperately looking for a revenue stream, notably believing contaminating all news regarding browser technology with its presence is the way to go.

The last thing the world needs is a predatory vendor trying to force itself somewhere it's not needed. Its non existing market share is the proof.

Re:Wikipedia Is Now a Brave Verified Publisher by omnimus on Thursday August 29, 2019 @04:09PM (#20833118)
I think he meant build on Gecko/Servo not Blink.
Re:Wikipedia Is Now a Brave Verified Publisher by marichards on Thursday August 29, 2019 @05:54PM (#20834099)
Whatever Mozilla's focus is when you load Firefox you experience the following:

1. On ESR first time it loads two pages load including

https://www.mozilla.org/en-GB/firefox/60.8.0/firstrun/ https://www.mozilla.org/en-US/privacy/firefox/

You then find first party cookies are set by Google Analytics

_ga GA1.2.1671101194.1567114471 _gat_UA-36116321-1 1 _gid GA1.2.377831647.1567114471

In the EU this would breach the ePrivacy Directive - as there is neither consent or information supplied in advance. Privacy is not just about information captured about you, but about privacy of what you have stored on your electronic devices.

Note: https://ico.org.uk/about-the-ico/news-and-events/news-and-bl... Myth 2: Analytics cookies are strictly necessary so we do not need consent

2. If you then type "privacy" into the address bar, it loads https://www.google.com/search?q=privacy&ie=utf-8&oe=utf-8&cl... directing users into the most privacy invasive service on the internet with no advance warning. I now have a wealth of Google cookies from their search domain, but there are also cookies set for DoubleClick and Adservices.

I'm now enrolled into surveillance capitalism and all I did was open Firefox for the first time, type "privacy" and press enter.

Mozilla talk a lot about privacy, but their products and websites don't live up to the privacy standards we need and if anything they're on the wrong side of the fence when it comes to acting on privacy - they still make things worse and not better; although it has to be acknowledged that they have improved a lot with the tracking protection features that have slowly been making their way into Firefox.

You might find this interesting to read https://twitter.com/jonathansampson/status/11658588961766604...

Re:Wikipedia Is Now a Brave Verified Publisher by Vinnl on Friday August 30, 2019 @03:37AM (#20836593)
Relevant context:

1. Mozilla only enabled Google Analytics after signing a contract with Google that that data would not be fed into Google's models. There's no reason to believe Google would violate that legal agreement.

2. The Twitter thread you linked is by a Brave employee. It should be judged by the facts it shows, but is good context to keep in mind w.r.t. their presentation.

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @03:10PM (#20841610)
Are you at Mozilla? That contract was referenced in a bug long ago. I'm not sure it can be enforced, given how Google's revamped Analytics 360 works.
Re:Wikipedia Is Now a Brave Verified Publisher by Vinnl on Saturday August 31, 2019 @05:03AM (#20845307)
No I'm not. I'd imagine that a contract would be enforced by both parties respecting it, especially given that there's not that much to win for Google, and much to lose if, say, an employee would leak that it was being violated.
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Saturday August 31, 2019 @01:19PM (#20847560)
Let's see the contract and its term, if not hear from Google that it is in effect. Sorry, but reputable blockers block GA because it is now tied into Google's overall ads/data business and they say as much in touting it, in their privacy policy even with its carve-outs, and in others' experience with it.

For Mozilla to use GA instead of self-hosted Matomo is odd to me as a founder of mozilla.org (none are left at Mozilla now, FYI). We do the latter at Brave. Is it just for convenience?

Re:Wikipedia Is Now a Brave Verified Publisher by kerkeslager on Thursday August 29, 2019 @06:05PM (#20834172)
You're right.

Do you have a better solution? I'm not asking to be glib, I actually want a browser that does a better job of protecting my privacy.

Re:Wikipedia Is Now a Brave Verified Publisher by marichards on Thursday August 29, 2019 @07:03PM (#20834546)
No solution, but I think we'll never find one if debate, about problems with web privacy, suggests Mozilla is the answer - until they put into actions their words, they shouldn't be seen as the way to go.

Whilst I have reservations about Brave, from a privacy standpoint they appear to be more trustworthy and some of the actions they are involved with, like complaints to regulators are far beyond anything we've seen of Mozilla - sure they may have corporate motives, but right now they appear to align far better with consumer privacy.

There are forks of Firefox that are trying to improve on delivery of privacy

https://tracker.pureos.net/w/pureos/policy/purebrowser/

https://github.com/intika/Librefox

I am not wholly comfortable using Brave because of its dependency on Chromium, too much of a dependency on a single web rendering engine reminds me of IE days.

I would suggest to anyone, install them both and more, you might love browsing the web in emacs (someone must) - if you find a website that doesn't work on Firefox and you need Chrome, then why not use Brave instead?

Personally I'm trying both, I also bought a Librem Laptop so I have PureBrowser too and I'm not afraid to throw some of my money and inconvenience at products that are better at protecting my privacy: for techies we can all do this with relative ease. For non-techies, which is where we really need the sea of change (and who are unlikely to read this), then we can advise them towards Apple's products and make them aware of products like Brave so it can be their "backup" browser if not their first choice - not perfect, but I'd prefer my family to browse using Safari, Firefox (with privacy settings I have to sit down and sort out for them) or Brave; than Chrome.

Re:Wikipedia Is Now a Brave Verified Publisher by kerkeslager on Friday August 30, 2019 @11:58AM (#20839811)
> Whilst I have reservations about Brave, from a privacy standpoint they appear to be more trustworthy and some of the actions they are involved with, like complaints to regulators are far beyond anything we've seen of Mozilla - sure they may have corporate motives, but right now they appear to align far better with consumer privacy.

There's a lot for me to think about in your post, and most of it I agree with, but I wanted to comment on this bit. While I agree that Firefox has made some very problematic decisions over the years, Brave is far worse in my opinion. My biggest 3 objections are here:

https://news.ycombinator.com/item?id=20830069#20833942

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @07:27PM (#20843635)
I can't find anything from you at that link.

Would you mind inlining your biggest 3 objections? Thanks.

Re:Wikipedia Is Now a Brave Verified Publisher by kerkeslager on Friday August 30, 2019 @08:40PM (#20843951)
It looks like my post fell off the front page, so the hashtag link doesn't work. :/ Copy-pasting my comment here:

Looking into this only briefly, it didn't take long to find a lot of very questionable decisions made by Brave:

1. They're positioning themselves as both an advertiser and a privacy advocate[1], which strikes me as more of a strategy for bootstrapping revenue than a trustworthy moral position. The entire point of crypto micropayments is to pay for content with crypto rather than attention/privacy. Why should I view Brave's ads rather than the other ads on the internet from advertisers who also claim their ads respect privacy? The fact that Brave has decided to get into bed with advertisers at all shows they're committed to profit, not to users: micropayments are just a way to diversify for Brave, which will quickly fall to the wayside if it fails to provide the revenue they want.

2. The entire concept of a Brave Verified Publisher stinks. It positions Brave as a censor. If this system takes off, then suddenly Brave has control over who gets paid for content on the internet, and can censor content they don't like. And this isn't hypothetical, they plan to do this: their TOS[2] explicitly contains a code of conduct which contains a long list of things they will terminate your account for: they promise to use their power as censors to enforce of US copyright/patent law and also a wide variety of subjective social norms. This also shows their commitment to being an advertiser rather than an application that serves users: if you're serving users then you let them pay for the content they want to pay for, but if you're serving advertisers, then you can't let advertisers brands be seen as supporting questionable content.

3. BAT based in Ethereum seems to be basically a way to ride the wave of cryptocurrency hype while still positioning themselves as a central authority/middleman. If they weren't trying to position themselves as a middleman, they would just make the micropayments in Ether directly, or better yet, in a cryptocurrency that doesn't have a history of forking the blockchain to fix an bug in a major users' contract[3]. If they weren't trying to ride cryptocurrency hype, they'd just allow micropayments via a much-simpler-and-more-reliable REST API or similar since they're already the central authority anyway.

I don't think we can trust Brave with our privacy or attention. I don't think we can trust Brave with the decision of who gets paid for content. I don't think we need Brave as a middleman to pay content publishers. I don't like the state of how content is paid for on the internet, but I don't think Brave is the solution.

It's disappointing to me that Wikipedia has decided to associate their name with Brave's. A big part of why I respect Wikipedia is their long-standing policy of keeping independent from advertisers, and it seems naive of them to have not realized that Brave is an advertiser. I can understand why Wikipedia has made this decision, but I still think it is a compromise of Wikipedia's values, and I hope they'll reverse their decision in the future.

[1] https://brave.com/brave-ads-waitlist/

[2] https://brave.com/terms-of-use/

[3] https://www.coindesk.com/ethereum-executes-blockchain-hard-f...

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @09:15PM (#20844056)
Too many words, I'll use fewer.

1. Ad spend last year was over $100M in the US alone, ~$300M globally. Heading toward $1T globally. Users subscribing or paying out of goodwill won't cover this if we block it all and corner the market. We are doing anonymous and private ads (also donations and subscriptions, note well), no conflict with user in data or revenue share. Read my comments here, e.g., https://news.ycombinator.com/item?id=20841558. For you to claim a conflict, you have to show we make more than the user, cheat the user, or somehow steal or leak data to our advantage.

2. We are in the middle phase of a multiyear roadmap, where the last phase will distribute domain verification to many oracles, if we can't bake it into validators on-chain. If you know of an existing blockchain solution, please lay it on us. Also for handling OFAC and other KYC regulations (where we use Uphold today). We cannot intermediate ad revshares, and no blockchain today can either. We do not censor, our test for domain ownership or channel control is objective. If you think we won't get on to phase 3 of our roadmap, fine -- but don't use your speculations as if they were facts.

3. Here is a chart from end of 2017 showing relative volatility. BAT was 2nd least volatile above USDT, we beat Bitcoin and Ether. But we also have other advantages via BAT, including our user growth pool. If you discount that then you are arguing we should find a billionaire to replace it with Ether out of the grace of his or her charity. Who might that person be? Your argument here is cheap unless it's you.

https://twitter.com/woonomic/status/942921951252709376

I don't find these to be objections based on reason so much as misunderstandings or hostile speculations that we will fail. You aren't required to agree with us, we're not imposing any system on you. If you don't like BAT, just use Brave with its default settings. If you don't like Brave, there are lots of other browsers. If you have rational arguments against any bug or design flaw in our intentional work to replace surveillance with privacy tech for donating and advertising, I'm all ears.

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Saturday August 31, 2019 @11:31AM (#20846857)
$100B of course, my B key turned into an M key lol.
Re:Wikipedia Is Now a Brave Verified Publisher by kerkeslager on Saturday August 31, 2019 @12:00PM (#20847078)
1. If you're saying that it's impossible to make money without accepting money from funders whose motivations conflict with users', that just means that a for-profit organization is not the way to build a browser that serves users.

A "conflict of interest" doesn't necessarily imply that you've done anything wrong yet, it merely says that the incentives are strongly in favor of you doing something wrong. In my experience, that means that when the cards are on the table you will do the wrong thing, not because you're a bad person or anything, but because you don't want to give up your funding and business.

It may just be that making a lot of money and serving users are fundamentally incompatible. And anyone who actually wants to prioritize serving users over making a lot of money needs to at least be open to that possibility. I really hope they aren't incompatible, for both your sake and mine--I'd like to be rich as much as anyone.

2. This is a non-reason. Domain ownership is already verified by certificate authorities, and there's no reason anyone should trust your centralized authority more than CAs centralized authority. In the very best case, where you do exactly what you're claiming you're going to do and allow other oracles, you've pointlessly reinvented CAs. But you haven't gotten there yet, so right now it just looks like you've created a CA system where you're the only CA, which is objectively worse.

If you want a blockchain solution, fixing the bugs in Namecoin[1] would be a start, although admittedly that technology has yet to play out in practice. It's possible a similar system could be implemented on top of BAT. The difficulty here is that you'd be reinventing the DNS system in tandem.

Let's be clear here, your TOS says you can censor people based on subjective criteria.[2] So if you claim "we do not censor", why don't you say that where it's legally binding?

3. So if you're arguing volatility is the issue, why didn't you just use USD? If you needed funding--again, that's your problem, not one users care about. You don't get a free pass on technology decisions that harm users just because they helped you get funding.

I am genuinely sad that corporations have proven themselves untrustworthy so many times that I can't trust you. As I've said elsewhere, you seem like a decent person with good intentions.

[1] https://www.namecoin.org/

[2] "As a condition of use, you promise not to use the Service for any purpose that is prohibited by the Terms of Use. For purposes of the Terms of Use, the term “Content” includes, without limitation, any information, data, text, photographs, videos, software, scripts, graphics, and interactive features generated, provided, or otherwise made accessible on or through the Service. By way of example, and not as a limitation, you shall not (and shall not permit any third party to) take any action (including contributing any Content) that: would constitute a violation of any applicable law, rule or regulation; infringes any intellectual property or other right of any other person or entity; is threatening, abusive, harassing, defamatory, libelous, deceptive, fraudulent, invasive of another’s privacy, tortious, obscene, offensive, or profane; constitutes unauthorized or unsolicited advertising, junk or bulk e-mail; contains software viruses or any other similar computer codes, files, or programs; or impersonates any person or entity." -- quoted from https://brave.com/terms-of-use/ , note that later it says, "Brave may terminate your access to all or any part of the Service at any time if you fail to comply with these Terms of Use, which may result in the forfeiture and destruction of all information associated with your account."

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Saturday August 31, 2019 @12:37PM (#20847331)
I will be brief, as replies growing ever longer is a bad condition. Also I do not want to argue about imponderables.

I’m aware of Namecoin, whose Wikipedia page says

“A 2015 study found that of the 120,000 domain names registered on Namecoin, only 28 were in use.[12]

Onename co-founder Muneeb Ali on 12 September 2015 at the Blockstack Summit 2015 stated that the Namecoin network is not decentralized and the mining group Discus Fish controls 60-70% of its hashing power.”

I was at the 2015 Blockstack Summit and can vouch.

I already noted we will distribute if not decentralize publishers verification. Namecoin can’t do YouTube or other UGC accounts, as we do. Handshake might pan out for domains, we are in touch. In our current Gemini phase we have to comply with laws, but we won’t kick out or unverify a site or channel based on legal content it hosts. Our rep would be trashed if we did.

This may be where we part company. I’m well aware of conflicts of interest and the difference between intentions and outcomes from Mozilla and prior experience. Brave nevertheless has put its reputation at stake, with open source and incremental work to decentralize as much as possible. We may fail for lots of reasons, but going bad and trying to steal from our users is highly unlikely. It would be quickly defeated. This is by design.

Re:Wikipedia Is Now a Brave Verified Publisher by kerkeslager on Saturday August 31, 2019 @03:42PM (#20848390)
We were never really likely to reach any agreement, so I'm fine with parting ways as amicably as is possible given that we disagree so fundamentally. I really do wish you the best; I hope I'm wrong and that you succeed in a way that's good for users.
Re:Wikipedia Is Now a Brave Verified Publisher by aaron_m04 on Thursday August 29, 2019 @10:46PM (#20835575)
I have a collective solution but not an individual solution: pressure Mozilla to change.
Re:Wikipedia Is Now a Brave Verified Publisher by kerkeslager on Thursday August 29, 2019 @10:54PM (#20835611)
This is the direction I'm currently on.
Re:Wikipedia Is Now a Brave Verified Publisher by pastastickers on Thursday August 29, 2019 @06:42PM (#20834431)
They might need an Apple-like "courage" moment, and replace Google with DuckDuckGo or Startpage as their default search service.

Come to think of it, I would expect the same move from Apple as well, on Safari.

Re:Wikipedia Is Now a Brave Verified Publisher by snazz on Thursday August 29, 2019 @07:03PM (#20834544)
That would kill their primary revenue source. I agree, it needs to be done. Hopefully the new Mozilla CEO will figure out a way to do it.
Re:Wikipedia Is Now a Brave Verified Publisher by doctor_eval on Friday August 30, 2019 @02:37AM (#20836381)
Safari/DDG user here. Presumably Firefox could load the search results into a container that throws away all the cookies after the search is done. Doesn’t it work like that for FB?

Presumably, the real problem is that this would be against Google’s terms of the agreement between google and. moz, but - at least technically - there is no reason to throw away access to google if that’s seen to be a desirable default.

Of course - I’m guessing that google is gonna add its own tracking variables to URLs, so any search result returned by google really is going to be suspect regardless of what we do.

Re:Wikipedia Is Now a Brave Verified Publisher by ksynwa on Thursday August 29, 2019 @08:22PM (#20834921)
GNU Icecat?
Re:Wikipedia Is Now a Brave Verified Publisher by codehalo on Thursday August 29, 2019 @07:28PM (#20834681)
The downvotes you are receiving for pointing out facts illustrates the cesspool of Firefox hypocrisy that hacker news has become.
Re:Wikipedia Is Now a Brave Verified Publisher by nothrabannosir on Thursday August 29, 2019 @07:56PM (#20834802)
Honestly typing "privacy" into a UI that is designed to act as a search field for Google, and blaming that on Mozilla somehow, that's a stretch. What's next? Typing "which company faked the moon landing" and WOW you're redirect to Google! It must have been them.

It's nothing but opinionated. You can't honestly call this a "fact" and go on to claim that HN is hypocritical. That's... is there a word for hypocrisy about hypocrisy?

(The first point made is not even that bad, it's just that quagmire following it which dilutes the whole thing)

Re:Wikipedia Is Now a Brave Verified Publisher by marichards on Thursday August 29, 2019 @08:53PM (#20835078)
If Mozilla wanted to respect privacy the "UI that is designed to act as a search field for Google" could be a "UI that is designed to act as a search field for DuckDuckGo", it wasn't that long ago it was a search field for Yahoo. What's notable here is that Google is the default and in doing so is endorsed and recommended by Mozilla for its users.

So the fact here is that Mozilla made that choice to be in bed with Google.

The sad irony is Chrome on Android will insist on asking users for the default search engine choice (in the EU at least https://www.techspot.com/news/81273-google-android-users-eur... ).

Maybe think about it another way. Imagine Greenpeace defaulted to offering to book supporters private planes to get to every protest. It is this nature of extreme distance from organisational values that Mozilla is expressing when it defaults to Google search.

Re:Wikipedia Is Now a Brave Verified Publisher by riquito on Thursday August 29, 2019 @10:51PM (#20835599)
Let's completely neglect in those "facts" that Google offers the best search engine and that people want to use it
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @03:12PM (#20841639)
Brave defaults to Google in most countries, but we get paid $0 for it. We also disable auto-suggestions based on key by key tracking to Google as you type your search term, leaving it as an option some users choose to enable.

This isn't that hard (except for doing without the big bucks, which is hard: Brave is building up small revenue to large, not profitable yet -- again, we pay the user >= what we make, 70% of gross revenue for user-private ads, 15% for publisher partnered ads [not yet launched]).

Re:Wikipedia Is Now a Brave Verified Publisher by marichards on Wednesday September 11, 2019 @06:32PM (#20945530)
I'm saddened that Google is the default. I hope Brave asks users in the future, but understand there are probably a few different goals being juggled whilst Brave grows.
Re:Wikipedia Is Now a Brave Verified Publisher by rjf72 on Friday August 30, 2019 @12:31AM (#20835989)
I think that ship has pretty much sailed, but in either case that has nothing to do with Firefox's decision. If they wanted to use Google, for whatever reason, they could do so while supporting user privacy by piping it through e.g. Startpage.

They just want the Google $$$, privacy be damned.

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @06:13PM (#20843192)
I won't violate any NDA still binding me to Mozilla by agreeing that the default search deal in Mozilla is and historically has been done for funding the company. If they wanted to switch, they could -- but it would hurt financially, big time. That could imperil the project as a whole. It would definitely limit salaries at the top.
Re:Wikipedia Is Now a Brave Verified Publisher by reportgunner on Friday August 30, 2019 @03:46AM (#20836620)
What happens when you turn on chrome or brave ?
[dead]
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @09:04PM (#20844023)
You've been downvoted, but your words deserve a reply. Profit motive does not go away in a "non-profit" (Mozilla Corp is the for-profit subsidiary of Mozilla Foundation; top salary last seen [2017] was $2.3M+). It takes innumeracy or worse to miss that Mozilla depends for its profits (to pay such salaries and bonuses) mainly on the Google search deal.

In my opinion, this conflict of interest between users and Mozilla's search revenue share held back tracking protection in Firefox over the years.

Meanwhile Brave has a transparent rate card, where we pay the user 70% of the gross revenue for user-private ads, and 15% for publisher ads (not yet deployed; the publisher makes 70% and we take same as the user). So we get <= what users get, and will fail if our users don't like the private/anonymous ad model enough to opt in at sufficient scale that we can cover our costs.

Good luck pressuring Mozilla to cut its top exec's pay from seven figures. Your words are empty.

[dead]
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Saturday August 31, 2019 @11:29AM (#20846841)
Mozilla says I was not fired: https://blog.mozilla.org/blog/2014/04/05/faq-on-ceo-resignat.... Are they lying?

On “racist”, you are wrong. But you seem to have trouble with the truth, so I will stop here.

Re:Wikipedia Is Now a Brave Verified Publisher by Ididntdothis on Thursday August 29, 2019 @01:27PM (#20831668)
“ I wish it was built on Firefox instead of Chromium. “

I commented in another thread. This is one area where Mozilla has failed. It should have been the goto engine for projects like Electron or Brave or even MS Edge instead of Chromium. But the last time I looked Mozilla was not very friendly towards developers who want to use their engine.

Re:Wikipedia Is Now a Brave Verified Publisher by dmix on Thursday August 29, 2019 @01:33PM (#20831734)
Everyone is also switching to headless chrome for automated testing since it's faster than Gecko.

I don’t know if FF has changed in this regard but it takes a long time to get rid of a perception of poor performance and this should have been their first priority long ago (which seems to be the case with their Rust work and GeckoView/mobile preview browser). In addition to how far they were behind Chrome security wise for so long, such as isolated tabs.

But I agree, this should have been Mozilla's niche that they owned. Owning the early adopters is critical to mainstream success IMO. We're the ones that regular people listen to when making tech choices.

Re:Wikipedia Is Now a Brave Verified Publisher by londons_explore on Friday August 30, 2019 @11:43AM (#20839665)
They still don't have isolated per-domain render processes... That means if I exploit any renderer, I can take all your cookies for online banking and your webmail.
Re:Wikipedia Is Now a Brave Verified Publisher by pbhjpbhj on Thursday August 29, 2019 @05:20PM (#20833815)
Presumably they don't want to split their Google funding.
Re:Wikipedia Is Now a Brave Verified Publisher by bsclifton on Thursday August 29, 2019 @12:05PM (#20830723)
(Brave employee here)

Curious: what are some of the shortfalls you see in Chromium?

Before I joined Brave, the desktop browser was originally using Gecko (from Firefox). Ultimately, there were some problems and the decision was made to move to Chromium. On iOS, Brave is forked from Firefox though

You can check out more detail on Reddit where folks asked why FF was not used (which has links to more detailed info): https://www.reddit.com/r/BATProject/comments/9jpqde/brave_br...

Re:Wikipedia Is Now a Brave Verified Publisher by phjesusthatguy3 on Thursday August 29, 2019 @01:07PM (#20831431)
>Curious: what are some of the shortfalls you see in Chromium?

That it's a Google-controlled project. Seriously, that's it. I have no reason to believe Google has my best interest at heart.

Don't turn that around and say "Oh, you think Mozilla is looking out for you?" because I don't. I just trust Google less.

Re:Wikipedia Is Now a Brave Verified Publisher by skybrian on Thursday August 29, 2019 @01:59PM (#20831997)
This is kind of silly. When you copy open source code, it doesn't give any magic access to the people who wrote it. If there is anything wrong with it, it has to appear on the source code somewhere.

The question you should be asking is whether you trust Brave to vet the source code and remove anything that seems like a problem.

Re:Wikipedia Is Now a Brave Verified Publisher by phjesusthatguy3 on Thursday August 29, 2019 @02:23PM (#20832223)
It isn't silly. How about I don't trust either one of them?

Brave is (and you are) saying I should trust Brave because they're going to rip out Google's tracking and insert their own instead. No thank you. I'll stick with Firefox and whatever chicanery Mozilla is up to.

Re:Wikipedia Is Now a Brave Verified Publisher by Ajedi32 on Thursday August 29, 2019 @02:52PM (#20832477)
If you don't trust Brave, how would that be any better if they were using Firefox as the base for their browser over Chromium?
[dead]
Re:Wikipedia Is Now a Brave Verified Publisher by furyofantares on Thursday August 29, 2019 @03:40PM (#20832877)
It’s just confusing because then your original comment is a non-sequitur, not particularly relevant to the context of the discussion about trusting Brave on FF vs Brave on Chromium, because, as you say, if you don’t trust Brave then the base doesn’t matter.

There isn’t any whataboutism in the post you are replying to.

Re:Wikipedia Is Now a Brave Verified Publisher by phjesusthatguy3 on Thursday August 29, 2019 @04:01PM (#20833050)
No, you didn't go back to my original post, which said I don't trust Google. My apology was about the language I used.
Re:Wikipedia Is Now a Brave Verified Publisher by Buge on Friday August 30, 2019 @12:24AM (#20835964)
I still don't understand why you would prefer if Brave was based on Firefox instead of Chrome. One of your comments sounds like you're worried about Brave inserting tracking. Brave could do that regardless of what it's based on.
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @03:15PM (#20841658)
No, we rip out Google's tracking and insert nothing.

Brave Ads are opt-in and client-based. There is no server side tracking of users or data in the clear. I can say more on how all this works, but I will pause here. Search for "catalog" elsewhere to find another comment explaining it a bit more.

Re:Wikipedia Is Now a Brave Verified Publisher by underwater on Thursday August 29, 2019 @11:32PM (#20835769)
Absolutely not silly. By shipping a Chromium-based browser they weaken Gecko and Firefox. A real risk is that we are left with Blink and Webkit being the only two engines. That makes it easier for Google to use their influence to push for standard changes that benefit them (see: DRM).
Re:Wikipedia Is Now a Brave Verified Publisher by bsclifton on Thursday August 29, 2019 @02:15PM (#20832155)
The team has been capturing deviations from Chromium on a wiki page here: https://github.com/brave/brave-browser/wiki/Deviations-from-...

The page goes over (high level) how the project is built and links to patches where functionality was disabled or modified (ex: proxied, etc)

Re:Wikipedia Is Now a Brave Verified Publisher by craftyguy on Thursday August 29, 2019 @09:03PM (#20835121)
It's not silly. Google 100% controls upstream chromium, and they can afford to make decisions about it in a vacuum.
Re:Wikipedia Is Now a Brave Verified Publisher by root_axis on Thursday August 29, 2019 @10:17PM (#20835456)
So what? Brave does not have to incorporate every decision from upstream.
Re:Wikipedia Is Now a Brave Verified Publisher by craftyguy on Friday August 30, 2019 @01:43AM (#20836197)
They would be screwed if google decided to actively cut off downstream chromium projects by making breaking code changes, licensing changes, etc.
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @03:16PM (#20841677)
Many browsers would be screwed, and Google would for some of the code be in breach of the open source licenses governing the file or library. It's not likely for that and for many other reasons, but who knows? Anyway by the time Google went this evil, we'd hope to be big enough to do our own engine.
Re:Wikipedia Is Now a Brave Verified Publisher by criley2 on Thursday August 29, 2019 @02:21PM (#20832211)
IMO just because it's open source doesn't mean it's safe.

I would trust a closed source project that has been thoroughly and extensively vetted by a third-party auditor I trust far more than an open source project that has no audit for me to reference.

As I am not a professional security auditor, my ability to understand the minutiae of developer decisions (intentional and unintentional) in some multi-million-LOC project is basically a limit approaching zero. My looking at the source code to give myself a false sense of security would only increase my risk, IMO.

It's like a restaurant tells you "yeah we have a clean kitchen, you can go take a quick look yourself!" and it's like, do you know to check that water and disinfectant buckets can't be within x feet of each other? To temp every fridge and warmer to ensure no danger zones? To monitor glove usage and hair net usage? And a thousand other things?

Being open source basically means that a nice auditor could do some audit work for free to help the community, but that's about it from my perspective.

Unless some of you are actively code reviewing the entirety of Chromium prior to launching any build of it ???

Re:Wikipedia Is Now a Brave Verified Publisher by tlb on Thursday August 29, 2019 @03:21PM (#20832712)
Can you give an example of a closed-source project you trust because it has been audited by a third party?
Re:Wikipedia Is Now a Brave Verified Publisher by kbrosnan on Thursday August 29, 2019 @08:21PM (#20834917)
Just about all certificate authorities are trusted by billions of people a day to encrypt their data. Almost all of CAs are privately held companies, the only way they are trusted is by being audited by a third party. For info about the inclusion process see https://www.ccadb.org/ and https://wiki.mozilla.org/CA/Information_Checklist

LetsEncrypt is an example of a non-profit open source based CA.

Re:Wikipedia Is Now a Brave Verified Publisher by TheArcane on Thursday August 29, 2019 @01:19PM (#20831580)
The deGoogle movement has been gaining steam ever since the ad-block announcement, and I'm a 100% behind it
Re:Wikipedia Is Now a Brave Verified Publisher by dmix on Thursday August 29, 2019 @01:35PM (#20831756)
Which happened after Brave launched.
Re:Wikipedia Is Now a Brave Verified Publisher by kerkeslager on Thursday August 29, 2019 @04:49PM (#20833517)
Okay, but it's not like Brave couldn't have seen that coming. It doesn't take a genius to see that a browser run by one of the world's largest advertisers is going to prioritize advertisers over users.
Re:Wikipedia Is Now a Brave Verified Publisher by dmix on Thursday August 29, 2019 @10:49PM (#20835589)
I’m just speaking from personal experience as someone who defended Chromium for quite a long time and finally hitting my peak. I’m sure I’m not alone.
Re:Wikipedia Is Now a Brave Verified Publisher by andrenotgiant on Thursday August 29, 2019 @01:52PM (#20831929)
I'm curious - how are the two related? What's the significance of the fact that Brave launched, _and then_ Google changing the extension API in a way that affects ad blockers?
Re:Wikipedia Is Now a Brave Verified Publisher by dmix on Thursday August 29, 2019 @01:58PM (#20831976)
The argument against using Chromium has increased significantly with that move.

Before you could argue that the open source Chromium was largely immune to Google's various small bad behaviours, but when they make such a large close-minded move, at a certain point you can't keep supporting the platform as a whole when they are so hostile to the open internet. Even if it's indirect support.

Also, it can't be ignore that Firefox's recent move towards parity with Chrome has played a big role in giving people the option to even switch.

Re:Wikipedia Is Now a Brave Verified Publisher by bad_user on Thursday August 29, 2019 @01:40PM (#20831817)
> On iOS, Brave is forked from Firefox

You mean the platform that specifically disallows competing browser engines, making Firefox just a shell over a Safari-enabled web view and that can't even access Safari's content blockers? The only Firefox that's not running a Firefox engine under the hood? That Firefox?

Given you're a developer for Brave, it's not possible for you to not know this, therefore your statement is misleading at best.

The pitfalls of Chromium are obvious... it gives Google the power to impose on the market whatever engine feature they want, they are the ones defining the web standards and there's nothing Brave can do about it because Brave does not have the capacity to maintain a full fork, or to fight for web standards, just like it doesn't have the capacity to build a browser without piggybacking on somebody else.

Don't get me wrong, nowadays even Microsoft admitted total defeat, but then Brave should recognize its total dependence on Google and its continued goodwill.

Re:Wikipedia Is Now a Brave Verified Publisher by csharp on Thursday August 29, 2019 @04:57PM (#20833578)
(iOS engineer at Brave here) All iOS browsers are based on webkit. WKWebView, which is what we use, does have full access to content blockers. This is how we do ad-blocking, HTTPSE upgrades, and script blocking.
Re:Wikipedia Is Now a Brave Verified Publisher by bsclifton on Thursday August 29, 2019 @03:06PM (#20832582)
You're right - all browsers on iOS (as far as I know, including Chrome) are wrappers around Safari. I didn't mean to imply Brave on iOS was based on Gecko, simply that it was originally forked from Firefox on iOS

We do have upstream contributions to Chromium. Nowhere near as many as Microsoft (we may only have a few), but we do try to contribute back when possible

Re:Wikipedia Is Now a Brave Verified Publisher by jefftk on Thursday August 29, 2019 @02:15PM (#20832154)
> Brave should recognize its total dependence on Google and its continued goodwill

What do you mean? Brave is based on Chromium, which is open source. Google can't stop people from using it.

(Disclosure: I work for Google)

Re:Wikipedia Is Now a Brave Verified Publisher by input_sh on Thursday August 29, 2019 @04:13PM (#20833164)
Google is the dictator of what gets accepted into Chromium and what does not. That's how open source development works -- even if the code is available to everyone, its maintainers control its future.
Re:Wikipedia Is Now a Brave Verified Publisher by jefftk on Thursday August 29, 2019 @04:52PM (#20833539)
Regardless of how Chromium is run [1] Brave is still in a position to make their browser work however they want. They can choose what Chromium features to enable, and take the code any direction they want.

[1] Your categorization doesn't match what I've seen. Microsoft has been driving substantial changes as Edge moves onto it.

Re:Wikipedia Is Now a Brave Verified Publisher by ryacko on Thursday August 29, 2019 @04:15PM (#20833195)
More significantly, (as far as I know) there is not much open discussion about Chromium’s goals or roadmap. The reduction of Adblock blacklists in Chromium was announced, there wasn’t some public mailing list where a flame war began over it.
Re:Wikipedia Is Now a Brave Verified Publisher by jsgo on Thursday August 29, 2019 @12:16PM (#20830851)
Not OP, but I'd imagine that it is Brave seems to be a browser that advocates for the user (and presumably in the future, publishers too with the pay thing). As such, the ideals seem more aligned with Firefox than Chrome (and by extension, Chromium).

Basically, you guys are in a weird space where your decisions aren't looked at purely from a technical lens, but also an ideological one.

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @03:20PM (#20841710)
Welcome to current year.

But don't let browsers pretend to be neutral runtimes for the terrible third party scripts on which surveillance advertising depends. They are not neutral. The big-4 browsers in the west apart from Apple are partly or fully captured by $100B ad businesses.

We are all in a weird space. Best to fight back at the endpoint with the right browser. Could be Safari, Firefox, or Chrome with opt outs and uBO and other defenses (but risks remain in Chrome especially), if you are not game for Brave.

Re:Wikipedia Is Now a Brave Verified Publisher by jsgo on Tuesday September 03, 2019 @11:05AM (#20867179)
Not saying you guys are wrong, just saying where it seems you get blowback for what another vendor doing more or less the same thing wouldn’t even register as a talking point. Not saying it’s fair, but it seems people hold you to something of a righteous/ideological expectation that Google et al can’t meet so they don’t even complain of it there.

In my mind, considering the push you’re making, you’d validate that vanilla chromium meets the requirements to achieve said push. If it didn’t, it’d be a non-starter and you’d have went a different route (leveraging aspects of Firefox’s stack maybe if, again, it met requirements).

Re:Wikipedia Is Now a Brave Verified Publisher by vorticalbox on Thursday August 29, 2019 @12:15PM (#20830842)
The monopoly google has over the web standard is probably the biggest issue.
Re:Wikipedia Is Now a Brave Verified Publisher by eikenberry on Thursday August 29, 2019 @01:20PM (#20831584)
Multi-account containers have become Firefox's killer feature that will keep me from switching. They are super handy for separating work accounts, managing my kids accounts, etc. while never having to worry about logging out of my primary accounts.
Re:Wikipedia Is Now a Brave Verified Publisher by basch on Thursday August 29, 2019 @12:33PM (#20831024)
being firefox on iOS is somewhat irrelevant to the rendering engine discussion tho, because iOS is forcing webkit on all its browsers, firefox is just a chrome around webkit.
Re:Wikipedia Is Now a Brave Verified Publisher by TheArcane on Thursday August 29, 2019 @01:20PM (#20831587)
Easy. Google has a lot of influence over Chromium development.
Re:Wikipedia Is Now a Brave Verified Publisher by pbhjpbhj on Thursday August 29, 2019 @05:27PM (#20833884)
Presumably they also have a veto, at least, on Firefox development as they're paying handsomely for it?
Re:Wikipedia Is Now a Brave Verified Publisher by stjohnswarts on Friday August 30, 2019 @02:20AM (#20836320)
Mozilla project would dissolve before they let google tell them how to make their browser
Re:Wikipedia Is Now a Brave Verified Publisher by TheArcane on Friday August 30, 2019 @02:23PM (#20841127)
They're paying to let FF make Google it's default search provider
Re:Wikipedia Is Now a Brave Verified Publisher by pbhjpbhj on Saturday August 31, 2019 @11:51AM (#20847016)
Yes, and you think Google will keep paying regardless of how they develop? If there's not review system in place then Google must be extremely poor at negotiating contracts and conducting business relationships. Similarly Mozilla probably would be reckless to not even know that a change would cause their primary source of income (100s of millions $USD) to stop.
Re:Wikipedia Is Now a Brave Verified Publisher by steveharman on Thursday August 29, 2019 @01:27PM (#20831667)
Any idea when Brave will support password sync across machines / devices? It's a bit of a limitation right now.
Re:Wikipedia Is Now a Brave Verified Publisher by balaksakrionon on Thursday August 29, 2019 @11:58AM (#20830648)
agreed, everytime i am in the settings and elsewhere i realize i'm using chrome and hate myself for a moment
Re:Wikipedia Is Now a Brave Verified Publisher by option_greek on Thursday August 29, 2019 @01:23PM (#20831625)
Brave being based off chrome is actually great and your comment illustrates that. If it is based on FF, it will cut into FF market share which is already shrinking. Now, it cuts into Chrome which means two privacy focused browser instead of one.
Re:Wikipedia Is Now a Brave Verified Publisher by barnabee on Thursday August 29, 2019 @01:50PM (#20831904)
What? It’s a separate browser, it cuts into the market share of whatever the user was using before.
Re:Wikipedia Is Now a Brave Verified Publisher by skinnymuch on Thursday August 29, 2019 @02:00PM (#20832008)
It cuts into market share regardless. Why would market share changes matter for browser engine?
Re:Wikipedia Is Now a Brave Verified Publisher by jchw on Thursday August 29, 2019 @12:01PM (#20830672)
IIRC it was actually originally Firefox. I wonder what exactly made them switch?
Re:Wikipedia Is Now a Brave Verified Publisher by jonathansampson on Thursday August 29, 2019 @12:18PM (#20830876)
This is correct. Note that both of our founders are from the Firefox team originally. Our CTO, Brian Bondy, originally built the first Brave prototype on the Gecko engine. Unfortunately, after much testing, it was clear that a modified Chromium would be the better route forward. You can imagine this was not a decision taken lightly, as both of these individuals have lived and breathed Gecko/Mozilla for years prior.
Re:Wikipedia Is Now a Brave Verified Publisher by Ididntdothis on Thursday August 29, 2019 @01:28PM (#20831680)
It doesn’t speak for Mozilla that even with these people Chromium turned out to be the better option.
Re:Wikipedia Is Now a Brave Verified Publisher by sp332 on Thursday August 29, 2019 @02:48PM (#20832443)
Mozilla has been admitting that Gecko is a huge drag since around the time they decided to break the extension model.
Re:Wikipedia Is Now a Brave Verified Publisher by toyg on Thursday August 29, 2019 @07:32PM (#20834702)
Actually, they have said so for much longer. The fact they started writing a completely new engine (Servo) in early 2012 was in itself an admission of defeat -- so many "embeddable Gecko" projects have been started and killed, over the years, that the only way forward is to replace with something new.
Re:Wikipedia Is Now a Brave Verified Publisher by reportgunner on Friday August 30, 2019 @03:50AM (#20836637)
>lived and breathed Gecko/Mozilla for years prior

but they don't anymore ? So if someone lives and breathes policeman life and then becomes a drug dealer, is it just like buying drugs from a policeman ?

Re:Wikipedia Is Now a Brave Verified Publisher by orblivion on Thursday August 29, 2019 @12:58PM (#20831342)
Would the story be different with Quantum now?
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Thursday August 29, 2019 @01:17PM (#20831543)
No, the decision was based on a spreadsheet with many items concerned with web compatibility, HTML5 DRM plugin free-as-in-beer, extension support, etc.

Chromium without Google tracking is dominant, this is just a fact (it will change some day; not soon). The best way to counter this is not to die on the wrong hill (engine wars) right now -- it is to go a level up and fight for privacy and user sovereignty where Google cannot defend: blocking all tracking, paying users 70% of user private ad revenue.

Re:Wikipedia Is Now a Brave Verified Publisher by lol768 on Thursday August 29, 2019 @01:43PM (#20831844)
> No, the decision was based on a spreadsheet with many items concerned with web compatibility, HTML5 DRM plugin free-as-in-beer, extension support, etc.

This is a spreadsheet I'd be interested to see. Was this compiled before or after Firefox supported WebExtensions?

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @03:06PM (#20841582)
This was in late 2015, but WebExtensions support in Firefox is never complete vs. Chrome, and you are ignoring DRM and all the other junk (gmeet screen sharing extension! ChromeCast! the list goes on... Chrome is the new IE, but at least most is open source or free as in beer).
Re:Wikipedia Is Now a Brave Verified Publisher by xtracto on Tuesday September 10, 2019 @05:00PM (#20933677)
> or free as in beer

IE was also free as in beer.

Re:Wikipedia Is Now a Brave Verified Publisher by input_sh on Thursday August 29, 2019 @04:16PM (#20833204)
"Fighting for privacy" and third-party ads do not belong in the same sentence.
Re:Wikipedia Is Now a Brave Verified Publisher by codehalo on Thursday August 29, 2019 @07:59PM (#20834819)
You are correct. That’s why it’s not in the sentence. Brave blocks third party ads by default.
Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Friday August 30, 2019 @02:54PM (#20841482)
Lotta green handles fibbing about us here.

We don't do third party ads. We block third party tracking which takes out third party and most first party ads. We also block fingerprinting, cryptomining, and other threats.

Re:Wikipedia Is Now a Brave Verified Publisher by input_sh on Saturday August 31, 2019 @02:04AM (#20844847)
> We don't do third party ads.

Are the ads hosted by the websites your users visit? If not, they're third-party ads, with you being that third party.

> Lotta green handles fibbing about us here.

Oh don't worry, I'd make the exact same comment from my other (non-green, thousands of karma) profile, I just like to occasionally switch aliases.

Re:Wikipedia Is Now a Brave Verified Publisher by BrendanEich on Saturday August 31, 2019 @11:50AM (#20847013)
The contract-based party numbering, first and third remain in common vocabulary, does not distinguish the browser or user as zeroth party. Putting tags on a page that cause tracking ads to run from unrelated businesses and their servers is the only useful “third party ad” definition here. Browser-based ads that use anonymity tech are a different category.

If you insist on a reductionistic definition that rules out anything other than a static ad on the same site as the publisher, you will get stuck trying to improve the Web and how it is funded. I understand objecting to all ads other than static images that click through into same origin forms, or whatever, but that won’t pay the bills for most publishers.

Re:Wikipedia Is Now a Brave Verified Publisher by Semaphor on Thursday August 29, 2019 @07:56PM (#20834801)
While I don’t like Brave, from what I’ve read the ads are decided on locally, so no information is sent to the advertiser. Again, this is what I’ve heard.
Re:Wikipedia Is Now a Brave Verified Publisher by reportgunner on Friday August 30, 2019 @03:52AM (#20836649)
Yes, perfect. I absolutely want to download ALL ads instead of NO ads.
Re:Wikipedia Is Now a Brave Verified Publisher by jonathansampson on Friday August 30, 2019 @03:11PM (#20841631)
With all due respect, that isn't how the solution works. Users must first opt-in to Brave Ads. Once they do, they download a regional catalog. This is a text document, compressed down to about 3 MB in size. Your machine (via on-board machine-learning) studies this for relevancy. When a relevant ad is found, you are given 70% of the revenue, and a notification is displayed on your operating system. You have control from the start, even over the frequency of ads you'll see within an hour.
Re:Wikipedia Is Now a Brave Verified Publisher by onyva on Sunday September 01, 2019 @09:09AM (#20852086)
Why would anybody be interested in this? Content that depends on ad revenu especially written for it, is not worth consumption. The idea of solving a non existing problem is the problem with AdBuddy (AKA Brave). The way to go is ad and tracking blockers and let advertisers find a way to get to users without exploiting their ignorance. I don’t care and don’t need to build a relationship or accommodate a publisher. This is not what the internet of for.
Re:Wikipedia Is Now a Brave Verified Publisher by buboard on Thursday August 29, 2019 @12:24PM (#20830933)
If anything i see it as the revenge to chrome