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, 2:59:58 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

31 sources
Brave excises quite a bit of Chromium[1], but that isn't what makes it fast and lightweight. The real savings come by way of not having to download all of the cruft of the Web. For many sites, more than 50% of the data loaded consists of ads and trackers[2]. When you don't have a sea of third-parties dropping scripts and more onto your machine, the Web is quite a bit more enjoyable [1] https://github.com/brave/brave-browser/wiki/Deviations-from-... [2] https://www.nytimes.com/interactive/2015/10/01/business/cost...
In Brave Introduces Brave Today, the Privacy-Preserving News Reader
There are more problems facing the Web than just "Google". Removing Google is good, and necessary, and solves a lot of problems. It's why we excise much of Google and Chromium from our own code-base with each update [1]. Blocking harmful ads and trackers is a necessity; users were already doing it in growing numbers before Brave came along. But this trend, while it yields safer users, cuts into the support given to the sites we visit and love. And asking users to send money to sites isn't necessarily a solid solution either. So Brave aims to address both issues: 1) User Privacy, and 2) Creator Support. What's interesting about this is that Ads are both the problem and solution. But not in their present form. Presently, ads on the Web harvest user information, auction it off to third-parties, and build up profiles on remote servers, far be
Read the rest
yond user control. Brave's privacy-respecting ad model uses client-side matching against regional catalogs (avoiding fingerprinting) with machine-learning. This model ensures privacy. And when an ad is displayed, 70% of the revenue goes into the user's cryptographically-secured wallet. This is where the second challenge (supporting content creators) comes in. As you browse, the ad-revenue you've generated gets queued up for the sites you visit. The privacy-respecting ads you view are translated into real-world support for the sites you visit. This is one of the reasons why users prefer Brave. We aren't trying to solve half of the problem; we're trying to reform the Web such that it remains free, equitable, and open. [1] https://github.com/brave/brave-browser/wiki/Deviations-from-...
In Brave Introduces Brave Today, the Privacy-Preserving News Reader
I tried out Brave a few years ago and soon noticed it did not completely clear history on close when configured to do so. While the history was not shown in the UI, you could see it was retained because URLs visited in previous sessions were shown in :visited style (links were purple instead of blue with default CSS. Note that this can also be queried via JS and thus allows sites to extract your browsing history). I reported the issue at the time but they said the won't fix it since they were moving away from brave-laptop. They still had issues[1] clearing forms of local storage year later. They are not taking privacy seriously. They also took crypto from users under the false pretense of taking payment on behalf of content creators[2]. [1] https://github.com/brave/brave-browser/issues/9929 [2] https://en.wikipedia.org/w/index.php?title=B
Read the rest
In Cover Your Tracks
We don't replace Google's account based tracking with anything of the kind. See https://github.com/brave/brave-browser/wiki/Deviations-from-... In completely unrelated code paths, all open source, we have timing-channel blinded, few bits per answer, automated survey questions that tell us, e.g., how many people reset default search to a different engine (but nothing more). See https://brave.com/privacy-preserving-product-analytics-p3a/. I'm not sure why you wrote what you wrote. Assumption? It makes an ass of u and umption, to quote Samuel L. Jackson's character from "The Long Kiss Goodnight" :-/.
In Brave Browser Passes 20M Monthly Active Users and 7M Daily Active Users
Brave is interesting because it's taking a firehose to the current ad-tech system, and anyone who's spent time working in ad-tech understands it's is a towering inferno of fraud and abuse. Some don't like Brave's approach of an alternative, opt-in ads / rewards system because in their view everything crypto-related or ads-supported is scammy. That's an understandable perception: a significant number of crypto enthusiasts appear to be scammers pumping pyramid schemes, and we've already established the ad-tech industry is a towering inferno. But technically I think you have to concede Brave's on-device ad relevance model is a better way (and the only conscionable one) to run an ad system that delivers relevant ads to interested users, and even directly reward them for their attention. If you think ad-supported anything is a non-starter, the
Read the rest
n you'd just never enable Brave Rewards, or use another browser (although they're entangled in the current ad-tech system so...) What you say about 'VPN fallacy' makes little sense. By default Brave is the most aggressive in blocking trackers, adware, and spyware compared to Firefox and Google — and this is actually a problem for Brave. Follow their web-compat issues on Github [1] to see the kind of things they're dealing with (an example of the very problematic and kind-of-unresolvable issues that come up include the Duolingo issue [2]). Users can disable shields on a per-site basis to deal with these things, but it's an open question as to whether this kind of friction will increase or decrease, and whether it's a barrier to larger adoption. There is no question though that the Brave team have the most commitment to privacy compared to Firefox and, of course, Google. Your statement that the Google spyware Brave has removed in their Chromium derivative has been replaced by some mystery sauce is based on...? I do find it curious that whenever this little challenger brand pops up on HN there's a predictable surge of hot take / bad take commentary which aggressively tries to paint a picture of Brave as anything but a plucky challenger brand full of technologists who are expending a lot of energy on privacy, security, and moving browsers forward. The accounts trying to shop a myth of Brave as a low-rent scam operation will inevitably find buyers for various reasons, but you'd hope technologists in the main will do their research and ignore, or even become curious as to what is driving this continued negative opinion-shaping... I did mine, and I fell for Brave due to a desire to opt-out of the worst of ad-tech surveillance, get a faster browser, and participate in a novel attempt to bootstrap a frictionless crypto / tipping / payment economy. Not all of these novel ideas will work, but they're worth exploring. For now Brave's been a dream, and when I accidentally use another open test browser for normal browsing, I'm taken back to a gross dystopia of a web experience. [1] https://github.com/brave/brave-browser/projects/17 [2] https://github.com/brave/brave-browser/issues/3725
In Brave Browser Passes 20M Monthly Active Users and 7M Daily Active Users
Relevant Brave (Chromium-based browser) bug discussion on exactly this: https://github.com/brave/brave-browser/issues/1127 They merged in a (partial?) bug fix in 2019: https://github.com/brave/brave-ios/pull/883 The underlying problem isn't that Google sites are directly excluded, it is that Local Storage, Database Storage, and Service Workers aren't cleared by that setting, and that Google uses those for persistence. Is this being evil or was support just not added when those were introduced? I have absolutely no idea. But I agree with fixing the underlying bug in Chromium either way.
In Chrome exempts Google sites from user site data settings
Google is hindering innovation around Chromium by refusing to merge upstream patches that may threaten their business interests, such as support for browser extensions on Android [1]. The same way no single megacorp can shape the Linux kernel according to their business interests, and to the detriment of competitors, it would be important to free the open source Chromium browser from Google's exclusive grip. [1] https://github.com/brave/brave-browser/issues/4493#issuecomm...
In Feds may target Google's Chrome browser for breakup
It will only be a matter of time before sites like Washington Post detect a Brave user and ask for instant transfer of BAT for access. Although Brave uses Chrome's UA, I think we can ask Brave for it's actual UA - https://github.com/brave/brave-browser/issues/8216 I give WashP as an example because they are extremely anti adblock and most subscribers see ads too. They also have very hard ways to opt out of third party tracking.
In Netflix boss: Remote working has negative effects

Showing the 15 most recent of 31 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.