not an attack but bad

hence NIP-89

Reply to this note

Please Login to reply.

Discussion

I think nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is saying the reverse. Explicit links to snort.social would get changed to nostr: links.

It would be pretty hard to do since there’s infinitely so many clients and different ways in how they approach constructing the URL. Should there be a NIP that specifies that shared Nostr web links should attach a query parameter so that 1) other clients know how to parse and navigate to the URL, 2) doesn’t mess with the path routing in the original web client if in the browser, and 3) works universally for links shared by any Nostr web client?

For example, https://snort.social/p/npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf?nostr=npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf (or whatever NIP-19 identifier)

Not a bad idea.

Maybe this fits in NIP-89.

I was just thinking of hardcoding a bunch of client rules.