DanConwayDev on Nostr: Here is a suggestion for updating the nostr:// git standard based on needs emerging ...
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://<optional-protocol/<required-npub>/<optional-relay>/<optional-relay-2..n>/<required-identifier>`
I'd love some feedback before implementing. fiatjaf (npub180c…h6w6) sommerfeld (npub16r0…z5pl) sommerfeld (npub16r0…z5pl) npub1uplxcy63up7gx7cladkrvfqh834n7ylyp46l3e8t660l7peec8rsd2sfek (npub1upl…sfek) GitCitadel (npub1s3h…75wz)
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://<optional-protocol/<required-npub>/<optional-relay>/<optional-relay-2..n>/<required-identifier>`
I'd love some feedback before implementing. fiatjaf (npub180c…h6w6) sommerfeld (npub16r0…z5pl) sommerfeld (npub16r0…z5pl) npub1uplxcy63up7gx7cladkrvfqh834n7ylyp46l3e8t660l7peec8rsd2sfek (npub1upl…sfek) GitCitadel (npub1s3h…75wz)