mirror of
https://github.com/status-im/status-go.git
synced 2025-01-09 22:26:30 +00:00
73a5189398
BridgeMessage is a type of chat message content which will be sent from Matterbridge. It contains fields: - bridge name - depends on the used bridge, eg. "discord", "slack", etc... - user name - username the message was received from - content - message content - user avatar - message id - parent message id - used in case of replies Message is saved to a separated table: bridge_messages, similarly to discord messages. The user_messages table is untouched. bridge_messages table contains user_messages_id in order to join with user_messages table. Issue #13098
status-go/protocol
This is an implementation of the secure transport and payloads which are a part of the Status Client specification.
This implementation uses SQLite and SQLCipher for persistent storage.
The payloads are encoded using protocol-buffers.
Content
messenger.gois the main file which exportsMessengerstruct. This is a public API to interact with this implementation of the Status Chat Protocol.protobuf/contains protobuf files implementing payloads described in the Payloads spec.encryption/implements the Secure Transport spec.transport/connects the Status Chat Protocol with a wire-protocol which in our case is either Whisper or Waku.datasync/is an adapter for MVDS.applicationmetadata/is an outer layer wrapping a payload with an app-specific metadata like a signature.identity/implements details related to creating a three-word name and identicon.migrations/contains implementation specific migrations for the sqlite database which is used byMessengeras a persistent data store.
History
Originally this package was a dedicated repo called status-protocol-go and was migrated into status-go. The new status-go/protocol package maintained its own dependencies until sub modules were removed and the root go.mod file managed all dependencies for the entire status-go repo.