So you're proposing to do away with using NIP-19 in URLs? If that's the case, I'm going to say that I'm not for it.

It normalizes using hex for everything and the real world use cases and counter argument is how many private keys I was given in the early days of Nostr Plebs instead of public keys, because users can't tell the difference.

I'd be fine using NIP-19 in URLs along with your proposed /p/, /e/, etc. Some applications already do this. There is no standard here. I'd be fine with that being the default for MKStack and making it the standard there. Just no hex!

Reply to this note

Please Login to reply.

Discussion

I agree with nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09ug4n6q3. NACK.

Having said this, naddr is problematic as the identifier isn't readable. Gitworkshop defaluts to nip05/identifier (if nip05 verifies) but supports /naddr or /npub/identifier or npub/relay-hint/identifier or nip05/identifier or nprofile/identifier

Is this proposal proposing to replace bech32 nostr urls with the hex version on these routes?