Just inquiring: I can understand the use case for coordination over nostr, but why store the git blobs on relays?
Git remote servers are already as decentralized as nostr relays. A single repo can be mirrored in any number of git remote servers over a variety of more data efficient protocols: http, ssh, ftp, etc.
Why not leverage that and focus on what nostr excels: social coordination, discovery, etc.
It comes down to the canonicity of the repository.
The canonical git repository is where all the action happens, regardless of how many mirrors you have. And this always ends up living on a single server.
I want to address the canonical repository with an event ID, and not need to care about who runs the server. I also don't want to use any credentials other than my keypair.
There's no canonicity in nostr since there's no global consensus and no shared state.
Dfferent users with different relays might see different repository states the same way different git remote servers might have different states.
I agree, but I think it's a lot easier to deal with multiple relays than it is to reconcile multiple git mirrors. I think this will become more obvious if places where git repos congregate come under attack.
