As far as I’m aware this is unsolved.
Ideally all this comms happens under the hood, so that the end user does not have to think about DM standards
nostr:nprofile1qqspwwwexlwgcrrnwz4zwkze8rq3ncjug8mvgsd96dxx6wzs8ccndmcpp4mhxue69uhkummn9ekx7mqprfmhxue69uhhyetvv9ujuem9w3skccne9e3k7mf0wccs6r48qf, nostr:nprofile1qqsy2ga7trfetvd3j65m3jptqw9k39wtq2mg85xz2w542p5dhg06e5qprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qyg8wumn8ghj7um0d3hkxmewdekz7atrpt7, et al:
Is anyone working on iOS Blue-style indicators, so that I know how best to reach someone via DM, and what to expect in terms of send success, etc?
Discussion
No question. This is crucial, hence my question. As it stands, there's no way to know what I'm using and if I should expect it to just work.
I understand and value the experimentation by devs.
I wonder if there is some low effort way to signal what DM standard my intended counterparty prefers.
cc nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
Yes, clients can look for recent events kinds of each protocol.
But the issue is that all clients must implement all protocols, which is never going to be the case.
No they don't. Clients should remove NIP-04 right now.
We should just kill NIP-04 as best we can. e.g. clients should just stop supporting it.
We should only really be using NIP-17 when it's low risk.
It's easy to check for user readiness to use MLS (and I think double ratchet too?).