My point is that we are pretending when you @ someone they will get it based on the relays you have configured. What an @ should mean in a social context is “make sure this note gets delivered to some well-known set of public-writable relays that the user has configured”. A big problem right now is that relays are hidden and there is no well-defined meaning of how a note should be delivered when you address someone.
Discussion
doesnt nip-05 have a section for defining a user’s relays?
I thought nip65 does exactly that
Yes I guess I didn’t appreciate how good it is until now. I thought it was just a relay list replacement, but it looks like it goes into specifics on how clients should read events from certain people. Will definitely implement this. In other words nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c is bad at marketing his nip or i was too busy to understand it until now.
I saw a new version of Camelus. So the development is still active, right?