What do you think about this alternate Nostr URL pattern idea?

## routes

Status quo:

- /:nip19 (eg naddr1..., nevent1..., nprofile1...)

Proposed:

- /p/:pubkey

- /e/:eventid

- /a/:kind/:pubkey/:d

## profile URLs

### nip19 (status quo)

https://nostrhub.io/nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhgprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shj4umzng

### proposed

https://nostrhub.io/p/0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd?relay=wss://gleasonator.dev/relay

## regular event URLs

### nip19 (status quo)

https://nostrhub.io/nevent1qqstspz3u2ygnm9qls34du9c6mvuazygzzepd780335c0qacvcl309qpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgvmmplj

### proposed

https://nostrhub.io/e/b80451e28889eca0fc2356f0b8d6d9ce888810b216f8ef8c698783b8663f1794?relay=wss://relay.primal.net

## replaceable event URLs

### nip19 (status quo)

https://nostrhub.io/naddr1qqrk66mnw3skx6cpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3qq3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnwsxpqqqpmejqquy09

### proposed

https://nostrhub.io/a/30617/0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd/mkstack?relay=wss://relay.nostr.band

Reply to this note

Please Login to reply.

Discussion

My brain likes this.

The proposed routers are not working yet?

It think it could be good to avoid the big encode string...

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!

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?

I use /e/ on nostrver.se for any event id and nip19 id

you can write your method in nip-89

No, Creates friction.

Before: user could just copy and paste whatever he saw into the browser

Now: copy and paste, find out that it doesn't work, find out why, find out he needs a conversor, spend time to find a conversor, download a conversor, install it, run it, paste, find out it doesn't work..

And once they know why (because e,p etc is missing), add it

People just won't do that