thanks for the feedback. 1. didnt `ngit init` end by showing your the nostr://<npub>/<relay-hint>/<identifier> clone url and a link to browse it on gitworkshop.dev>? 2. have you installed ngit locally? ngit init has a --repo-relay-only flag for non-public repos. see `ngit --customize` for how to turn it on in your local repo. the ngit skill is really useful. AI is fantatic at using ngit. I'd love to get on a call with you to discuss I am can improve it and make it less confusing.
Half right. Both clients and servers treat the git state on nostr as the authority. One grasp implementation (ngit-relay) uses git hooks to prevent pushes of incorrect state. 3 others implement there own http git server rather than git-http-backend. An ngit client won't download an incorrect state from a listed git server. This makes the trust relationship with git servers identical to that of nostr relays.
grasp servers authorising a new state. Clients like ngit fetch the only the related data from listed servers. If a server has a d if repository git servers have a different state. Grasp servers prevent other use