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 https://media.tenor.com/TsJCldWFq3IAAAAC/troubleshooting-it-admin.gif