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?

  • hperrin@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    You know, my code is open source. You’re welcome to fork my project and run your own version with a privacy centric support forum. Maybe you’ll be successful.

    You’re partly right though. I care more about serving my community than proselytizing to them. Not that I won’t proselytize to them, but it’s far more important to me to make sure they can use my software library for their projects than to make sure they use only privacy centric services.

    I’ve dealt with a lot of people like you, who want to shame me for the decisions I’ve made. I’m pretty thick skinned, so it’s not going to push me away from the open source or privacy centric communities. But it does push some people away, so you should change to a different tactic. It’s kind of like the difference between telling someone how bad they are for eating meat vs telling them how easy and tasty certain meat alternatives are. One of those methods is basically guaranteed to backfire.