this post was submitted on 21 Oct 2025
6 points (59.4% liked)

Opensource

4212 readers
375 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

CreditsIcon base by Lorc under CC BY 3.0 with modifications to add a gradient



founded 2 years ago
MODERATORS
 

My browser recommendation, if you're looking for something that's open source and pretty competent, it's a fork of Firefox with some pretty unique functionality.

you are viewing a single comment's thread
view the rest of the comments
[–] CameronDev@programming.dev 1 points 1 week ago* (last edited 1 week ago) (1 children)

I use Zen as well, but I dont like the idea of calling any browser fork "privacy focused". It only takes one malicious update and your entire online life can be exfilled to wherever.

You can sue Mozilla/Google/MS (maybe unsuccessfully, depends on functional courts) if something goes wrong there, you cannot sue a random github repo.

[–] moonluna@lemmy.world 1 points 1 week ago (1 children)

I max the settings on strictest privacy and I have extensions to manage the voids that may be there

[–] CameronDev@programming.dev 2 points 1 week ago* (last edited 1 week ago) (1 children)

Won't help if the browser exfils your data. You have to trust the browser no matter what.

[–] moonluna@lemmy.world -2 points 1 week ago (2 children)

Have you found an actual flaw in privacy?

[–] CameronDev@programming.dev 3 points 1 week ago (1 children)

No, this is (to my knowledge anyway) a theoretical problem. But it is very much a real risk, as demonstrated by the xz backdoor.

We should be very careful who we trust, especially for browsers, because a compromise could be catastrophic.

[–] moonluna@lemmy.world -2 points 1 week ago

I'm always cautious of all software. So fair warning

[–] Kissaki@programming.dev 3 points 1 week ago

The attack surface is the flaw. The chain of trust is the flaw/risk.

Who's behind the project? Who has control? How's the release handled? What are the risks and vulnerabilities of the entirely product delivery?

It's much more obvious and established/vetted with Mozilla. With any other fork product, you first have to evaluate it yourself.