3f987cc565
This commit ensures we're relying on `chat.DeletedAtClockValue` instead of `chat.Active` to know whether or not we need to remove the chat from paired devices. Because we were relying on `Active != true`, we ended up with a serious but that would result in deactivating all chats on paired devices. The reason the chats would disappear on paired devices is because, when setting up a new device by importing a seedphrase, chances are this device will receive `HandleBackUp` signals (which original from other devices with the same account that backed up contacts etc). When backups are handled, we create chats for every contact that's part of the backup signal. Those chats are set to `Active = false` because the signal handling shouldn't cause those chats to show up in the UI. However, because those are set to `Active = false`, the next time the user tries to sync from this devices, all those chats are considered as "removed", hence sending "chat removed" signals when syncing (which then causes those chats to disappear on all paired devices. We need to rely on `DeletedAtClockValue` to know whether a chat was indeed removed and only then emit such a signal. |
||
---|---|---|
.. | ||
anonmetrics | ||
audio | ||
common | ||
communities | ||
datasync | ||
discord | ||
encryption | ||
ens | ||
identity | ||
images | ||
internal/sqlite | ||
migrations | ||
protobuf | ||
pushnotificationclient | ||
pushnotificationserver | ||
requests | ||
sqlite | ||
subscription | ||
transport | ||
tt | ||
urls | ||
v1 | ||
verification | ||
zaputil | ||
LICENSE | ||
README.md | ||
activity_center.go | ||
activity_center_persistence.go | ||
anon_metrics_test.go | ||
chat.go | ||
chat_group_proxy.go | ||
chat_test.go | ||
communities_messenger_test.go | ||
contact.go | ||
delete_message.go | ||
edit_message.go | ||
emoji_reaction.go | ||
errors.go | ||
group_chat_invitation.go | ||
group_chat_system_messages.go | ||
identity_images.go | ||
local_notifications.go | ||
message_builder.go | ||
message_persistence.go | ||
message_validator.go | ||
message_validator_test.go | ||
messenger.go | ||
messenger_activity_center.go | ||
messenger_activity_center_test.go | ||
messenger_auto_message.go | ||
messenger_backup.go | ||
messenger_backup_test.go | ||
messenger_bookmarks.go | ||
messenger_browsers.go | ||
messenger_browsers_test.go | ||
messenger_chats.go | ||
messenger_communities.go | ||
messenger_config.go | ||
messenger_contact_requests_test.go | ||
messenger_contact_update_test.go | ||
messenger_contact_verification.go | ||
messenger_contacts.go | ||
messenger_delete_message_test.go | ||
messenger_discv5.go | ||
messenger_edit_message_test.go | ||
messenger_emoji_test.go | ||
messenger_ens.go | ||
messenger_handler.go | ||
messenger_handler_test.go | ||
messenger_identity.go | ||
messenger_identity_image_test.go | ||
messenger_images.go | ||
messenger_installations_test.go | ||
messenger_mailserver.go | ||
messenger_mailserver_cycle.go | ||
messenger_maps.go | ||
messenger_messages.go | ||
messenger_mute_test.go | ||
messenger_peers.go | ||
messenger_pin_message_test.go | ||
messenger_pin_messages.go | ||
messenger_response.go | ||
messenger_response_test.go | ||
messenger_share_image_test.go | ||
messenger_status_updates.go | ||
messenger_status_updates_test.go | ||
messenger_sync_bookmark_test.go | ||
messenger_sync_chat_test.go | ||
messenger_sync_clear_history_test.go | ||
messenger_sync_profile_picture_test.go | ||
messenger_sync_settings.go | ||
messenger_sync_settings_test.go | ||
messenger_sync_verification_test.go | ||
messenger_sync_wallets_test.go | ||
messenger_test.go | ||
messenger_walletconnect.go | ||
messenger_walletconnect_test.go | ||
persistence.go | ||
persistence_test.go | ||
push_notification_test.go | ||
status_update.go | ||
transaction_validator.go | ||
transaction_validator_test.go |
README.md
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.go
is the main file which exportsMessenger
struct. 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 byMessenger
as 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.