Subnostr

Designing a DM for a microblogging app is not the same as designing a chat app.

A chat app opts for better security while accepting poorer multi-device synchronization capabilities.

A DM opts for better multi-device synchronization capabilities while accepting weaker security.

We need to determine what our primary goal is, make trade-offs, and recognize that there is no perfect solution.

As reflected in the note below, the advantages and disadvantages of NIP-17 are two sides of the same coin. nostr:note1lscq8kz2huwnzngtdfqs22r7wlrasjy7uavcq22gjzxu8zawknqsvjy29d

Reply to this note

Please Login to reply.

Discussion

τέχνη 1y ago

Will you be participating in the MLS implementation for Nostr?

VictorieeMan 1y ago

There's good thought and clarity behind this note. I like the differentiation presented.

At the same time I do also think the future of nostr DMs are unclear. The metadata leak of the OG nostr dm standard is problematic and it's nor unreasonable for a new client to ignore implementing it in that basis alone. This do however leave us with an uncertainty of DMs in the nostr ecosystem. Because you'll never be sure about cross client compatability on the DM question.

And in the eyes of a normie that equals: "DM don't work."

Maybe we need gather around a new standard later down the line that becomes the de facto nostr dm.

Something is needed for use in exchanging propper chat app details etc.