External Publication
Visit Post

Wish for "clean" Brave Browser

Privacy Guides Community [Unofficial] April 10, 2026
Source

Menkork:

Could you just tell us what modifications have been done to improve it?

github.com/imputnet/helium

Does Helium inherit the security issues from ungoogled chromium (mDNS, etc.) ?

opened 11:50PM - 12 Dec 25 UTC

closed 08:03PM - 05 Feb 26 UTC

      Arjun127790
    

For your issue to not get closed without review, please confirm that: - [ x] Th…is issue does not fit into any of the predefined categories, which is why I am making a blank issue from scratch. - [ x] I am not reporting a security vulnerability through this issue, because I am aware that there is an appropriate channel for that. - [x] I understand that I will be permanently banned from interacting with this organization if I lied by checking any of these checkboxes. --- The ones spoken of from this site: https://qua3k.github.io/ungoogled/ ?

Menkork:

There’s also a supply chain weakness I’m seeing here

What is the problem with reporting a vulnerability if you already see it?

Menkork:

You’re still relying on a small team to merge upstream patches

So? You’re always relying on someone, and everything is built solely on trust, unless it’s Google Chrome, from a major company that’s also the developer of Chromium.

Menkork:

compile them on third party cloud servers

I’m sorry, what? What third-party cloud servers? What do you consider first-party?

Menkork:

Not to mention, they aren’t providing any sort of solution for MV2

What does that mean? Is MV2 supposed to be in the browser or not?

Discussion in the ATmosphere

Loading comments...