193 karma · joined December 31, 2014
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
The page goes over (high level) how the project is built and links to patches where functionality was disabled or modified (ex: proxied, etc)
The Rewards feature of Brave is what allows users to pay creators and also opt-into ads. This feature is completely optional though. It's off by default and users never get bothered about it
Brave is actually a proper fork of the Chromium code-base and builds on top of it, which is a lot more involved than a theme. The work that's been done is fairly significant if you wanted to give it a try. Even if you never enable Rewards, there are some great features and under-the-hood tweaks for privacy, Ad-blocking, and tracking protection
There's a list of ways that Brave deviates from Chromium here for quick comparison: https://github.com/brave/brave-browser/wiki/Deviations-from-...
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...
I reviewed with team and created https://github.com/brave/brave-browser/issues/3301 to track this (folks are welcome to give it thumbs up). The fix for this should be something we can deliver in our next product release (0.60.x - 9 days from now)
edit: issue is now fixed! https://github.com/brave/brave-core/pull/1633
I also captured feedback on being able to customize/opt-out of this functionality with https://github.com/brave/brave-browser/issues/3302 (thumbs up and comments appreciated!)
The JSON file that was linked to does have partner domains which (when the header is present) the website will provide a specific integration. When those specific partner sites are visited, the headers are sent with the request
An example someone mentioned here already is marketwatch. They have a promotion where you can sign up for a free subscription if you use Brave
The browser is open source and nothing is being hidden- although this and the whitelist (used for a better webcompat experience) could be better documented
Should these lists be shown in the UI and configurable? (ex: disableable?) I wonder what a better experience would look like for people that don’t want this functionality
Java isn't new or unpopular- if people wanted to use it, they would
- Microsoft didn't care about mobile, thinking Windows CE was fine (they had ~42% marketshare in 2007)
- Windows Phone 7 was great, but it was too late by then (2010... 3 years after iPhone was release and 2 years after first Android phone)
- There were two resets (7 => 8, 8 => 10) which screwed customers hard. With the 7 => 8 upgrade, not only were apps incompatible, the OS was incompatible with previous hardware.
- The App Store was mostly full of garbage apps (lots of fake apps- hard to fine the genuine app)
- Carriers didn't do a very good job pushing Windows Phone (can you blame them? :P )
From my perspective (former WP user, 2011 - 2015), the biggest WTF to me was when Microsoft bought Nokia. That seems to be about the time they just completely gave up
For example: this technology looks cool. How can I take advantage of QUIC to speed up my personal hosted content? Is there a module for nginx or an Apache mod_quic I can install? The code is out there of course, but it seems prebuilt options are limited
- Google has majority share of browsers with Chrome
- Chrome has QUIC enabled by default (opt out via chrome://flags)
- Google has a large amount of resourcing allocated to Chrome/Chromium. They ultimately control whether or not code is accepted
- Google also owns DoubleClick; ads are already being pushed using QUIC
- Regular end users are likely not aware of QUIC. Sure, a more advanced user can show it in the dev tools if you enable it and then look for it. But the problem is more that people aren't aware this is something to look for and they are opted into this
Showing a banner and trying to sell a product is one thing. But using a protocol that the user is not explicitly approving of to track / advertise is another thing. It seems to me (and maybe I'm wrong) that they are using their borderline-monopoly position in the browser market to opt people into questionable advertising technology
Only complaint I have about Edge is how Windows pushes it down your throat. You get while setting a different browser and even AFTER setting a default browser
More details: https://github.com/brave/browser-laptop/issues/7287#issuecom...
I love their vision, the services they provide, and what they've done here (with the donations) <3
Jonathan Sampson, author of the article, has been using similar methods to test popular extensions with Brave to ensure we have support for them (and if not, to identify what's missing).
You can track the progress that he and team have made here: https://github.com/brave/browser-laptop/projects/1
I'd also like to see more activity on the Twitter account or just more engagement with the community. You've got a killer product :)
Unfortunately, GitHub is where people expect open source projects to be, so it's almost an inconvenience for contributors to be on anything other than GitHub