This is cool but FOSS alternatives already exist for GitHub, such as Gitea. Pretty easy to setup and already mirrors a lot of GitHub functionality and fairly widely used. Why reinvent the wheel just to integrate Nostr? And if we do want to integrate Nostr with a Got service, why not just fork Gitea and add the Nostr stuff to it?
Discussion
There should be a "request edit" NIP, "git" not "got" haha.
Sometimes easier said than done to take a large existing project and rearchitect it to work under different assumptions. It can be done but it’s hard. Maybe with vibecoding, it’ll be easier. Someone (not me) should try it. :) Besides, it’s fun building things from scratch.
I think that this would be a great topic for a discussion with nostr:nprofile1qyg8wumn8ghj7mn0wd68ytnvv9hxgqgswaehxw309ahx7um5wgh8w6twv5qzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7p0junqg.
Thanks for the pointer, I'll check nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7qgswaehxw309ahx7um5wghxcctwvs666g7h out more.
There's actually already an API for GitHub, and I think they were going to do GitLab and Gitea, as well.
We're nostr-izing a git HTTP server, directly, as SaaS, and renting out tenants.
Oh that's awesome. Can I ask, what's the utility of adding Nostr here? Is it easier, better auth? I.e. a challenge to the email way of doing things?