179
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 11 Aug 2024
179 points (97.9% liked)
Open Source
31736 readers
123 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 5 years ago
MODERATORS
That's not the conclusion I have. The code is corrected and even if you don't trust the dev, the code is open and problems can be detected. It would be a problem if the developer did not acknowledge and correct the problem. It's 2 years ago and since then there wasn't an issue. But everyone can decide for themselves, I'm just speaking for myself.
While the code being open is good you still have to rely on trust.
I certainly don't have the time to review to code of each extension I use. And even then, we have no garanties that the extension distributed through the browser stores has the same code.
You can see the issue was opened on august 18th but the responsible commit was only made on the 19th. So the code was pushed the extension users before it was made available on the repository. Open code is of no help here.