Could you guys give the five-year-old explanation on how I could get 📁 Repos on a #communikeys Blossom server or Relay?
It's not even clear to me what parts would go where: Server vs Relay.
The code file = blob on server ?
The PR = ????
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 .
Could you guys give the five-year-old explanation on how I could get 📁 Repos on a #communikeys Blossom server or Relay?
It's not even clear to me what parts would go where: Server vs Relay.
The code file = blob on server ?
The PR = ????
The relay holds the repo announcement (that tells you which gitserver to interact with and which npub controls the repo), the issues/bug-reports, and the patches/code-change-requests, and the convos under the issues and patches.
You can use blossom to track git blobs, but it's a bit redundant. Mostly necessary, if your commits are really big.
Yeah code is on the gitserver, PRs are on the relays.