Messenger 2.0
Goals
- Refactor groups to have sub rooms
- Reintroduce notification digests for smaller groups
-
Deprecate newsfeed posts to a sub topic (for legacy support) - Understand relationship between groups, gatherings, conversations and messenger
- Refactor messenger to use own tables and support groups
- New encryption algorithm (Libsodium?)
- MindsID Asymmetric keys
Mark's Notes
Shared keys per conversations
The facilitate group chats and to avoid message duplication, we should have keypairs per conversation that can be unlocked by all parties involved.
Messenger Schema
Table name | ||||
---|---|---|---|---|
messenger_list | (user_guid | conversation_uuid) | pub_key | |
bigint | uuid | text | ||
messenger_conversation | (conversation_uuid) | shared_key | last_message_timestamp | |
uuid | text | timestamp | ||
messenger_members | (conversation_uuid | user_guid) | muted | |
uuid | bigint | bool | ||
messenger_messages | (conversation_uuid | message_uuid) | user_guid | body |
uuid | uuid | bigint | text |
Limitation of Messenger
- Max number of messages capped at 200 for performance
Asymmetric MindsID Keys
Asymmetric MindsID keys consist of a private key and a public key which contain keys needed to operate the Minds network. These keys are designed to be decentralized and operate across network. The fingerprint of these keys can also be stored on the blockchain.
The keys can also be used to control ETH based DiD profiles as they contain ETH keypairs.
Private Key (unencoded)
{
"schema": "v0.0.1",
"eth_priv": "0x0101030409697790dkdkw9192pdkoisehfoiw4hty039urho239y5029o4ehrtowei48y5y34out975",
"messenger_priv": "----",
"password_hash": "--- BCRYPT ---"
}
Public Key (unencoded)
{
"schema": "v0.0.1",
"eth_pub": "0x981903...",
"messenger_pub": "----"
}
Milestones
Milestone | Link |
---|---|
%Groups Q4 | https://gitlab.com/groups/minds/-/milestones/69 |
Merge Requests & Branches
TODO |
Mockups
TODO |
Developers
Developer | Focus |
---|---|
@markeharding | fullstack |
@edgebal | fullstack |
added scoped labels
changed the description
mentioned in epic &61 (closed)
changed the description
changed the description
added issue front#2155
changed title from to
changed the description
changed the description
I just want to make sure this path allows us to get off zulip. That's the key as soon as is humanely possible