Any of the other Nostr Devs out there know what to do when the event returns a P tag without a preferred relay? This seems to be pretty common. I've tried using the relay the tag came in on, but that seems to be mostly a miss.
The only thing I can think of is to shotgun common ones, but that doesn't feel right. #[0] , I'd appreciate if you could repost this for me to get more eyes on this. I'm at a loss and don't really want to shotgun it.
#[1]
I say shotgun it. Like to all connected relays. It's a cheap query.
done. But sadly it was very little help. I guess I just need to grow my relay list.
When events refer to people (or other events for that matter) without a recommended_relay_url and which are not present on the relay which served the referring event.... then you might be kind of screwed. I've been battling this myself. I keep event-relay and person-relay associations in a database based on everything the client has ever seen, and look up those associations and hope. But sometimes there are none to use (especially when starting off). I really appreciate clients that fill in the recommended_relay_url field. So far I haven't fallen back to the "configure read relays" fallback solution, but that does work in today's nostr environment better than you might think.
hopefully it becomes standard to make that mandatory. Even after shotgunning my measly list, I'm still missing a lot of profiles.
Oh, and followed (my public follow list is wrong, I dont update it)
My conclusion from this discussion with Michael is that he is currently building:
#[30]
