38
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Jun 2026
38 points (89.6% liked)
Open Source
47211 readers
200 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
As others have said it is a huge amount of work to maintain a fork of such a complicated piece of software.
Especially around security: web browsers constantly process potentially-malicious data, which gives them a large attack surface. Every browser regularly has new vulnerabilities discovered which must be fixed. Hard forking a browser means that, even ignoring any bugs in the new code the fork has added, every time a bug is discovered and fixed in the code they forked from someone needs to analyze the upstream's fix and port it to the fork. The more they diverge, the more work this is. Failing to do this work lets any malicious website exploit the bugs and install malware on users' computers.
A big part of me wishes the browser would just die. Its become a bloated and surveilled mess, entirely controlled by like 2 companies, with 90% of the actual data being javascript spyware. There's almost no browser that can't be fingerprinted and linked to your identity nowadays.
A simple markdown browser for static content (IE like gemini), and native apps with open APIs that can render markdown for dynamic content (IE like most fediverse apps), should be all we need.