Open Source

30956 readers

490 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Posts must be relevant to the open source ideology
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago

MODERATORS

[email protected]

157

Why FOSS projects are using proprietary, privacy invasive infrastructure? (lemmy.ml)

submitted 5 months ago by [email protected] to c/[email protected]

125 comments fedilink hide all child comments

As you can easily notice, today many open source projects are using some services, that are… sus.

For example, Github is the most popular place to store your project code and we all know, who owns it. And not to forget that sketchy AI training on every line of your code. Don't we have alternatives? Oh, yes we have. Gitlab, Codeberg, Notabug, etc. You can even host your own Gitea or Forgejo instance if you want.

Also, Crowdin is very popular in terms of software (and docs) translation. Even Privacy Guides and The New Oil use Crowdin, even though we have FLOSS Weblate, that you can easily self-host or use public instances.

So, my question is: if you are building a FLOSS / privacy related project, why using proprietary and privacy invasive tools?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 40 points 5 months ago (1 children)

Because most oss maintainers are more afraid of their work disappearing due to service shutdowns than they are being profiled by data miners.

Everyone has seen some example of a tool or resource hosted on a persons private server end up taken down because they couldn’t afford it, the isp or university stopped offering hosting or because they simply couldn’t keep doing it due to death or old age.

That’s what people who create software are afraid of. The loss of that creation, not the loss of the privacy of people who contribute to it or download it.

[–] [email protected] 9 points 5 months ago

Remember when we used to have mirrors as standard practice? If it is just text, it doesn’t use much space to serve someone else’s code too (no, your README does not need images, video, etc.). Besides, every node in a DVCS is a technically a mirror, it’s just decentralized collaboration is a lost art to many.