Post
For asknostr.site, I don't think there's going to be much risk that the notes would "belong" somewhere other than the author's outbox relays, so I don't think 𝐒𝐧@𝐱 has to worry about that. I definitely see where that would come into play for Flotilla, though. Vitor Pamplona mentioned that Amethyst encodes the first 3 outbox relays from the author's 10002, if they have one that can be found, or the first 3 relays the app received the note from, if no 10002 can be found. I wonder if it would be better to do something like, encode the first 3 outbox(write) relays from the author's 10002, so long as they have one AND the note in question can be confirmed to be available from those relays, otherwise encode the first 3 random relays that the app received the note from.
0
That would be ideal, but it's probably more of a job for clients helping users pick their relays. I've wanted to build a relay management client for a long time that checks relay availability, specs, policy, etc (directly and via nip 66), as well as probing the relay for user access. Then, warning the user if a relay goes down or misbehaves, and migrating notes back and forth when selections change. Clients shouldn't duct-tape the network together with broken heuristics if users can't be bothered to make good relay selections.
0