The biggest friction with #GitViaNostr onboarding is the git server setup. We have ideas to fix that with a nostr-permissioned git server implementation inspired by
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6's nostr:naddr1qqz8xmmwvupzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqvzqqqrhnyq32amnwvaz7tm8d96zuenfv96x5ctx9e3k7mg8rc3xy
We envision many public instances that allow user to push new repos with no signup and zero-configuraiton required.
Let me know if you would like this.
My biggest issue with Song currently is that I can't for the life of me get it to respond to the "smart" git protocol correctly.
If someone wants to fix that for me please do it!
Except for gitea, no other Golang implementation of a git server seems to be doing that, they all use the "dumb" protocol. And I can't understand the gitea codebase (haven't tried hard enough).
This is not even important, but since I failed at doing it I got tired and didn't finish implementing the proper NIP-34 features I wanted to, there is only currently a half-broken patch view UI that is not very helpful.
Oh also the server is lacking a proper view for standalone commits and standalone files.
We all get tired and are enthusiasm for things fluctuate :-)
Does song work with ngit? I raised this issue a few months ago when I tried to deploy it locally: https://gitworkshop.dev/r/naddr1qvzqqqrhnypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qqywdhkuec4lpj9u/issues/note1skr5kxfkphhwkyzeq6cn83apw7vs0vyshlumrk86644tj24vtzzs3hfj7z
I haven't tried yet. Someday I will.
