Free and Open Source Software

17915 readers

39 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

Gaywallet@beehaw.org

alyaza@beehaw.org

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

submitted 5 months ago by JustMarkov@lemmy.ml to c/foss@beehaw.org

38 comments fedilink hide all child comments

cross-posted from: https://lemmy.ml/post/15691030

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

[–] 520@kbin.social 9 points 5 months ago (1 children)

Because hosting shit yourself isn't free, and most people aren't up for taking financial losses for their projects.

[–] JustMarkov@lemmy.ml 5 points 5 months ago (2 children)

Gitlab, Codeberg, Notabug, etc.

[–] 520@kbin.social 3 points 5 months ago (1 children)

And how do they make their money?

[–] thisfro@slrpnk.net 5 points 5 months ago (1 children)

Gitlab: For profit (wouldn't say it's much better than github)
Codeberg: Donations
Notabug: unclear

[–] Shareni@programming.dev 5 points 5 months ago

Gitlab: For profit (wouldn’t say it’s much better than github)

It's got that added excitement that comes with a risk of someone doing a rm -rf on the production DB