xmtp / xmtp-js

XMTP client SDKs for JavaScript applications.

Home Page:https://xmtp.org/docs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Deprecate Conversation ID JS

nplasterer opened this issue · comments

Remove support for setting conversationId field for new conversations

Are we sure about this? The philosophical reason for convoIDs was that conversations were meant to be just that, transient communications, not permanent channels between identities. I probably missed a lot of what went on in the meantime, but my understanding was that we introduced deterministic convoIDs to deal with the duplicate convo problem, but does that mean that we have to do away with separating conversations altogether? Also a pragmatic reason for convoIDs was handling Lens profiles, how do we handle those without convoIDs?

Yep you're totally right. I was confused by some of the information floating around and this is actually just a docs change to let people know we no longer encourage setting it in most cases.