HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
brave
brave-browser
Web Development2018–2026
brave / brave-browser

brave-browser

Brave browser for Android, iOS, Linux, macOS, Windows.

145Distinct people
203Mentions
1Explicit recommenders
24.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Brave browser for Android, iOS, Linux, macOS, Windows.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

edit2: Nevermind all this, Brave did in fact implement protected content this earlier this year https://github.com/brave/brave-browser/issues/413 I still can't use brave to…

dkhenry used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:03:30 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year203 dated mentions

Observed mentions: 2018-06-21 03:22:42 UTC to 2026-09-28 20:15:01 UTC.

0102030402018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 30 mentions; 0 submissions, 30 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 31 mentions; 6 submissions, 25 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 43 mentions; 2 submissions, 41 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 32 mentions; 2 submissions, 30 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 22 mentions; 2 submissions, 20 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC11011
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC30030
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC31625
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC43241
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC32230
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC22220
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC13211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC11011
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC1019

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
Brave Browser This repository is not needed for building the browser and only holds issues, releases and the wiki. The source code and contributions are at https://github.com/brave/brave-core. You can visit our website to get the latest stable release. Resources Issues: Bug reports and feature requests for the Brave Browser. Releases: Releases of Brave Browser hosted on GitHub. See Brave Release Schedule for more information. Wiki: Documentation for developers, administrators, and power users. User-facing documentation is available at the Brave help center. Documentation and guides: Additional technical information, primarily for developers. Contributing Please see the contributing guidelines. To get started building Brave, hop over to the Wiki. Security Policy Please see the security policy. Community Join the Q&A community if you'd like to get more involved with Brave. You can ask for help, discuss features you'd like to see, and a lot more. We'd love to have your help so that we can continue improving Brave. You can also ask questions and interact in the community-guest channel on Brave Software's Slack. Help us translate Brave to your language by submitting translations at https://explore.transifex.com/brave/brave_en/. Follow @brave on X for important news and announcements.
Read the full README on GitHub

What Hacker News says

30 sources
Hi, I do privacy research at Brave. Our fingerprinting protections are still being improved (our second round of FP defenses should hit nightly in Jan), but the comments here are wrong; our defenses are much better than Firefox and Chrome. We don't consider as part of our threat model preventing sites from knowing you're using Brave. I'm not aware of any browser or tool that considers this as part of their privacy threat model either (including the terrific Tor Browser Bundle). Our goal is to prevent sites from distinguishing between Brave users. My claim is that our fingerprinting protections are strictly stronger than Firefox and Chrome. A partial list of fingerprinting protections that are enabled by default in Brave are at [1]. Fingerprinting is tricky, and we're tacking the problem in on multiple dimensions. We need to go further,
Read the rest
and expect to have v2 of our defenses in nightly in the next month or two [2], but we're also leading efforts in W3C to address fingerprinting in standards (I'm snyderp, those are my / Brave issues identifying privacy harm in standards) [3], and we're pushing hard to prevent web standards and privacy efforts from being eaten up by vaporware [4]. So, all that is to say, Brave has the most aggressive fingerprinting protections of any general purpose browser, and is getting better. The naysayers are welcome to backup their claims ;) 1: https://github.com/brave/browser-laptop/wiki/Fingerprinting-... 2: https://github.com/brave/brave-browser/issues/5614 3: https://github.com/w3cping/tracking-issues/issues 4: https://brave.com/brave-fingerprinting-and-privacy-budgets/
In Brave Isn't Bad
I didn't just follow it closely, I directly discussed it with Brave developers here and on Twitter at the time and I've continued to have to deal with their fraud for the last year. In their issue tracker an employee specifically called out me blocking them over this[0] to justify continuing to spoof their User-Agent. I am unfortunately still involved by having to burn more volunteer developer time and effort to block them. You claim I didn't make an honest or thoughtful criticism, but you didn't support that by disputing any of my facts or reasoning, and your only defense of Brave is that they were caught too early to successfully defraud anyone. Whether the money was taken directly from end users or indirectly from speculators in their ICO is irrelevant. They falsely represented themselves to users as site owners and they continue to ev
Read the rest
ade responsibility by falsely representing themselves to site owners as different users. It is tediously prudent to want nothing at all to do with a company that does business through misrepresentation as a standard practice. [0] https://github.com/brave/brave-browser/issues/4641#issuecomm...
In Brave Passes 10M Monthly Active Users, Sees 19% Growth Since 1.0 Launch
I've been using Brave for a few months, and I'm basically using it as an un-Googled Chrome. Not using the ad rewards system. It's pretty good, though I sometimes miss Safari with its amazing location bar autocompletion and ease of syncing with the iOS version. (Brave supports syncs, but it's not great, and the iOS app is nowhere as good as Safari on iOS.) Brave does have some bugs. Since July or so, several sites (including my bank) don't work because Brave incorrectly [1] blocks their cookies, even with the "shield" turned off. [1] https://github.com/brave/brave-browser/issues/6099 and several others.
In Brave launches 1.0
dkhenry·Nov 13, 2019Recommendation phrase
edit2: Nevermind all this, Brave did in fact implement protected content this earlier this year https://github.com/brave/brave-browser/issues/413 I still can't use brave to watch netflix on Linux. Its a great product and I love shifting the incentive of advertising away from intrusive data harvesting, but treating Linux like its a second class citizen means I won't use your product. Whats worse is that Firefox is 100% open source and Chromium is 100% open source and they both manage to get this working out of the box. There is no reason for Brave to not have working Netflix edit: Also I know the library that decodes the DRM is proprietary, my point is the integration with it is open and available, no reason it can't be duplicated.
In Brave launches 1.0
(Brave employee here) We block 3rd party ads and tracking, that collect user data, often without their knowledge or consent. Brave Ads are disabled by default, to ensure that no one sees ads that is not interested in viewing ads. This provides a benefit to advertisers as well, as they currently dump a lot of money into a dumpster fire, and are basically tasked with measuring how many of the pixels appeared on the screen for a certain amount of time. Brands don't know if people that viewed the ad were interested in advertising. People get shotgunned with ads. We're approaching this differently. We've introduced advertising that is private by default, with a new approach to measuring and accounting for ad event confirmations through our ad confirmation protocol. We have some information regarding the confirmation protocol here, for those i
Read the rest
nterested. https://github.com/brave/brave-browser/wiki/Security-and-pri... Aside from providing advertising that's private by default, our ad platform includes people in the process, by rewarding them for their attention (70% of the rev share for the ads viewed). People can then contribute those tokens to publishers and creators (like Wikipedia), or hold the tokens. In the future, people will be able to redeem tokens for gift cards, premium content, etc. We'll be introducing additional ad units in the future for publishers, with a cleaner deal and better rev share than they currently receive (publishers will receive 70% of the revenue, people will receive 15%, Brave will receive 15%). If we were just replacing publisher ads with other ads from the existing ad ecosystem, I'd understand and agree with the sentiment. That said, we're bringing new methods for ad delivery, accounting and matching to the market, all designed to function without leaking your information from your device. Hope this helps.
In Wikipedia Is Now a Brave Verified Publisher
(Brave employee here) 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-...
In Wikipedia Is Now a Brave Verified Publisher

Showing the 15 most recent of 30 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.