Here is a suggestion for updating the nostr:// git standard based on needs emerging from usage:
nostr://ssh/npub123/relay.damus.io/my-repo
nostr://npub123/my-repo?relayhint=relay.damus.io&server-protocol=ssh
nostr://naddr123*
*no support for specifying server protocol
note that `git clone nostr://...` will name the directory with anything after the final `/` unless a directory name is specified.
I personally think the first format has the best balance of conciseness and readability. To articulate it more precisely, rather than by example, it is:
`nostr://
I'd love some feedback before implementing. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5pl nostr:npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5pl nostr:npub1uplxcy63up7gx7cladkrvfqh834n7ylyp46l3e8t660l7peec8rsd2sfek nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz
I've implemented this with `?protocol=
I've also updated `ngit init` to default to using https clone urls, as this is the most sensible for fetch.
Given that most repo events include ssh clone urls, I'm tempted to just always use https for fetch and ssh for push (with a https fallback) unless the `protocol` override is used. push failures of ssh are instant whereas over https sometimes needs to be prompted for credentials.
Next up I need to actually implement the override.
No replies yet.
