Nostr clients need more support for `a` tags & `naddr` / `nevent` / `nprofile` IDs with embedded relay info. They’re incredibly powerful. Situations like in the pic shouldn’t happen. 
Discussion
Doing a test to see how different clients handle `nevent` (spec'd in NIP-19)… Both how they render it in kind 1 events and whether they handle it properly when you put it in as a search. Here's the nevent for the note this note is in reply to. It contains a relay hint of wss://relay.s3x.social - which should be all the clients need to find the note and display it. Let's see which clients handle it correctly…
Supporting `nevent` seems to be a work in progress with nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub1wnwwcv0a8wx0m9stck34ajlwhzuua68ts8mw3kjvspn42dcfyjxs4n95l8 …
Searches work great…
And when I went to reply, it worked great…
But in the normal timeline it still just shows the `nevent` value - it doesn't render like it should…
nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 Snort seems to fully support `nevent`…
The `nevent` is rendered properly in the feed…
And it works great in search as well…
nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch didn't handle either case well, but it's at an earlier stage of development - so that's somewhat expected.
nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg did the search properly, but I couldn't test how it looks in the feed since I can't figure out how to login (I seem to be locked into a read-only demo mode or something)…
