What are we supposed to do here? https://nostrcheck.me/media/1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411/4a252f6272bc6e743120c6cb3557fbab93626962886d5493285d05b46fdb1e7c.webp
Discussion
Unless you know exactly what relay you should connect to fetch this event in amethyst you cant do nothing.
I usually open the event in noStrudel and there it shows an option with a relay list to try to fetch the event if the event is not found
I long press the missing note, copy the note ID, then paste it to a new note, x it out so it goes to drafts, then check drafts. I'd say 3/5 times, that works to find the note without leaving amethyst. Its a janky work around
Clients still don't include relay or pubkey hints on quotes, so it often fails to load even in coracle. Super annoying.
There’s the whole auto-pilot/hints/the under the hood of where do I find this note, which is what nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn is describing.
There is also the UI affordance / signifier for this unhappy path. Normie end user doesn’t care about NIP-818, kind-7654 or relay hints.
They simply
1) observe “why is this broken”
2) ask why cant i find this
3) wait, is it still loading
4) how do i know if its still loading/searching, or if this process has concluded
5) ask wtf is all this, where can i learn more
From the screenshot from nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac only 1), and 2) are handled, and they are handled in a way that reminds of a windows 95 error.
This practically true for all apps, not just the app above. This unhappy path of multiple relays (as opposed to wikipedia, twitter, discord etc single server approach) is a strength, and weakness of nostr
