The spec specifically says only to use the designated relay list

Reply to this note

Please Login to reply.

Discussion

so these users events are missing the required read/write parameter or what?

or they can't be found?

if they can't be found then they should fall back to whatever they can find

solving the consistency problem is a high level architectural error in nostr, it doesn't need to apply for everything, but some things it does need to definitely be broadcast broadly, which blurs the line between relay and client, since you have to define some reasonable logic for this, and access control and ...

i have not enough emphasis capability in this medium to describe my yawning right now

If the user selection for inbox relay doesn't exist, the user has not expressed that he is using a client that supports nip 65. Any fallback relay will be invalid, since read/write 10002 relays may not even accept 1059s. The only correct thing to do is to surface the error (and hopefully help users fix it).

"may not accept" ok but they will sned to anyone who asks most of them

ah what a mess

So, Coracle cannot send/receive YakiHonne’s encrypted messages (I don’t know the NIP and all that)?

i've been saying it since that stupid nip-44 came out that it doesn't actually improve privacy or security, it just doubled the size of the tagget devs have to hit and nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr9mhxue69uhkscnj9e3k7unpvdkx2tnnda3kjctv9uqzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cez0c7vk7 here would like that anything can be deprecated but it's in the nature of this enterprise that we don't throw a new stepping stone in unless we anchor it properly, otherwise we get the mess we see now

I’m not sure what that means. What is the designated relay list?

Kind 10050. But you as a user don't need to know that. Just have the person you're talking to go to relays and add "DM Inbox" relays.

Ok so the error is about the users I am Dm’ing. That was my first point of confusion, thinking I had something configured wrong. But every DM shows this error, even ones where we are getting messages back and forth.

Coracle will still attempt to send stuff, and old-style messages will still be readable. Suffice to say it's complicated because of interoperability. Hopefully this will improve as more clients add support and UX gets more attention.

Ok, thank you.