Silberengel @Silberengel - 1mo
I think this is an important thing to do, to aid the migration of Nostr repos to Nostr. We could host a OS gitserver of our choice (like Gitea) in the cloud and build APIs to make it more Nostr-y, and then tie it into the GitStuff NIP-34 clients. Some individual devs have their stuff hosted on their own webservers, but smaller projects are stuck on GitHub. Leaving them open to censorship. Codeberg and etc. are just differently bad. And spreading everything out hinders collaboration. I don't think we'll ever get off GitHub unless we have someplace to escape to, and our name is nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz .
One of the "quiet struggles", on here, is WHERE DO I PUT MY CODE? The answer is almost always GITHUB, for 5 reasons: 1) It's free-to-use, which means you can stay anonymous and you don't have high financial overhead for small projects. 2) It's managed. You don't have to rent a server, buy a domain, update and monitor the server, renew certificates, blah blah blah. 3) Lots of other Nostriches are there, so if you leave a comment or PR, someone might see it and respond. 4) It gets lots of web traffic, so people can find your repo with a search engine. 5) The green blocks 🟩🟩🟩 stack up, when you interact with other repos, and grant committees and employers like that. That's why it's important that you contribute in a way that can be visualized with a contribution heat map. If we did this, it would at least give you 2 different servers to use, the second one would be payable in Lightning, and it would keep you from being rugged or being forced to use GitHub.
Laeserin @Laeserin - 1mo
One of the things we need is a Nostr repo contribution graph.... on Nostr.
mleku @mleku - 1mo
yeah, when it's available i will host my stuff on github for visibility and push to it in parallel but use the other place for kanbans, issues and CI/CD
