Doesnt this same critque apply to censorship resistant nature of social media on nostr? But with git servers rather than nostr relays? I suppose its harder to query git servers for whether they are storing a user's repository. In that scenario the maintainers could point to onion addresses which are harder to shut down?

Replies (3)

frphank's avatar
frphank 1 year ago
> I suppose its harder to query git servers for whether they are storing a user's repository. You should be able to query a server for "all repos signed by public key X" the same way you can query a nostr relay for "all events signed by public key X". But on nostr relays can just store your events without your involvement. A relay can mirror another one just by pulling events off of it. Your git server idea requires going back to the maintainer for each new server, the maintainer has to approve each new git server with a signed event that needs to be broadcast. So there's a bottleneck there.
frphank's avatar
frphank 1 year ago
Maybe ngit can be augmented with an element of discovery. Where basically the user tells it to find a repo just identified by a certain public key, and give it a list of servers to try. That would make it very nostr like.
This could work great for git server implementations designed to work with NIP-34 becausei repos could be addressable by, domain/pubkey/identifier a bit like how content is addressable in blossom. You could even have DVMs that could find git servers that serve the repo for you.