Fabio Manganiello on Nostr: nprofile1q…qumdy I fully agree on the code forge! Most of my stuff is now on my ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqel2c9kre8qm3g8sk6tzdj5cqnzu7sldqeqesrrm6aw9f6ac9jt0q3qumdy (nprofile…umdy) I fully agree on the code forge! Most of my stuff is now on my self-hosted Forgejo server. It didn’t even take much to set up and it doesn’t even require a lot of resources (unlike Gitlab). The big problem with this decentralized approach however is the lack of federation. At the current stage someone who wants to push a PR or open an issue on Platypush needs to create an account on my Forgejo instance. I’d love to be in a world where ActivityPub(-ish) protocols also apply to code forges, so I can use the same account to contribute to repositories that live on different servers, and my contributions to different instances are all visible on my instance, just like replies to accounts on multiple Mastodon instances. Forgejo started working on something like that a while ago, but I’m not sure if there’s been much progress.

About closing up FOSS, of course you can’t “close it up” strictly speaking, but you can sure decide what users can do with it. Same with GPL/AGPL - of course the code is accessible to anyone, but if you decide to redistribute it in a closed format or package it in your own closed cloud and profit from it, you are violating the license.

Of course such constraints aren’t easy to enforce, especially if you end up fighting legal battles against a powerful government, but it’s important to start setting precedents.