I think nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is saying the reverse. Explicit links to snort.social would get changed to nostr: links.
Discussion
✅ Optimism Airdrop Round 2 Is Live!
👉 https://telegra.ph/Optimism-Airdrop-Round-2-Is-Live-06-09 Claim your free $OP.
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)
^ nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn would y’all have appetite for a NIP that proposes query parameter hints on share links for maximum cross-client compatibility?
I was just thinking of hardcoding a bunch of client rules.