Oh, I didn't know there was a ?relay thing at the end because Coracle didn't display the URL and instead tried to render a preview.
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
basically you can add a query parameter with 'relay' in the name and it will decode the value. this way multiple relays can be specified. to prevent ugly encoding of characters like :// affecting the readability it will assume the wss protocol unless ws is specified.
this seems all seems a bit loose to me and may lead to clients producing urls that look different.
I personally like your way more (because of readability) and that's what I was thinking Nostr URIs would look like in general before bech32 encoding was introduced, but I still think it's better if we have a single canonical way of encoding things and naddr has more momentum (it's also easier to copy-paste if that matters). What do you think?
is it a problem if you can use either?
I've released there is a problem with the format. if you dont specify a directory name, git will use anything after the last `/`. so in this case it will add the ?relayhint=git.fiatjaf.com to the director name.
perhaps we should switch to the less intuative but still readable:
nostr:://npub123/git.fiatjaf.com/relay.damus.io/identifier
Would be neater. Would you still accept URIs without the relay?
yes, it might be able to find the event but its better to include a relay hint.
intuitive?
Yes, spelling error. But the new proposed format is shorter. I'm concerned about implementing loads of ways of doing it and forcing anyone else who wants to use the cloning syntax to do the same.
I have enhanced this suggestion here with the need to specify the protocol git should use to fetch / push to the git server as maintainers may want to push over ssh but fetch over https.
