status-im
/
status-go
mirror of https://github.com/status-im/status-go.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-go/protocol/protobuf/application_metadata_messag...

93 lines
2.9 KiB
Protocol Buffer
Raw Normal View History

Handle membership update message This commit does a few things: 1) Handle membership updates using protobuf and adds the relevant endpoints. 2) Store in memory a map of chats + contacts for faster lookups, which are then flushed to disk on each update 3) Validate incoming messages Sorry for the large pr, but you know, v1 :)
2019-12-02 15:34:05 +00:00
syntax = "proto3";
Sync Communities (#2253) * Added community sync protobuf * Updated community sync send logic * Integrated syncCommunity handling * Added synced_at field and tidied up some other logic * persistence testing * Added testing and join functionality * Fixed issue with empty scan params * Finshed persistence tests for new db funcs * Midway debug of description not persisting after sync * Resolved final issues and tidied up * Polish * delint * Fix error not handled on SetPrivateKey * fix infinite loop, again * Added muted option and test fix * Added Muted to syncing functions, not just in persistence * Fix bug introduced with Muted property * Added a couple of notes for future devs * Added most of the sync RequestToJoin functionality Tests need to be completed and tests are giving some errors * Finished tests for getJoinedAndPending * Added note * Resolving lint * Fix of protobuf gen bug * Fixes to community sync tests * Fixes to test * Continued fix of e2e * Final fix to e2e testing * Updated migration position * resolve missing import * Apparently the linter spellchecks * Fix bug from #2276 merge * Bug fix for leaving quirkiness * Addressed superfluous MessengerResponse field * Addressed feedback * VERSION bump
2021-08-06 15:40:23 +00:00
option go_package = "./;protobuf";
Handle membership update message This commit does a few things: 1) Handle membership updates using protobuf and adds the relevant endpoints. 2) Store in memory a map of chats + contacts for faster lookups, which are then flushed to disk on each update 3) Validate incoming messages Sorry for the large pr, but you know, v1 :)
2019-12-02 15:34:05 +00:00
package protobuf;
message ApplicationMetadataMessage {
// Signature of the payload field
bytes signature = 1;
// This is the encoded protobuf of the application level message, i.e ChatMessage
bytes payload = 2;
// The type of protobuf message sent
Type type = 3;
enum Type {
feat(pairing): sync 1-1 chats and groups on pairing devices (#4102) Fixes #3547
2023-10-17 13:24:15 +00:00
reserved 14;
reserved "SYNC_INSTALLATION_PUBLIC_CHAT";
Handle membership update message This commit does a few things: 1) Handle membership updates using protobuf and adds the relevant endpoints. 2) Store in memory a map of chats + contacts for faster lookups, which are then flushed to disk on each update 3) Validate incoming messages Sorry for the large pr, but you know, v1 :)
2019-12-02 15:34:05 +00:00
UNKNOWN = 0;
CHAT_MESSAGE = 1;
Add Commands (#1731) This commit adds handling of Transaction commands.
2020-01-10 18:59:01 +00:00
CONTACT_UPDATE = 2;
Handle membership update message This commit does a few things: 1) Handle membership updates using protobuf and adds the relevant endpoints. 2) Store in memory a map of chats + contacts for faster lookups, which are then flushed to disk on each update 3) Validate incoming messages Sorry for the large pr, but you know, v1 :)
2019-12-02 15:34:05 +00:00
MEMBERSHIP_UPDATE_MESSAGE = 3;
Always use protobufs by reference & generate handlers
2023-08-18 11:39:59 +00:00
SYNC_PAIR_INSTALLATION = 4;
DEPRECATED_SYNC_INSTALLATION = 5 [deprecated=true];
Add Commands (#1731) This commit adds handling of Transaction commands.
2020-01-10 18:59:01 +00:00
REQUEST_ADDRESS_FOR_TRANSACTION = 6;
ACCEPT_REQUEST_ADDRESS_FOR_TRANSACTION = 7;
DECLINE_REQUEST_ADDRESS_FOR_TRANSACTION = 8;
REQUEST_TRANSACTION = 9;
SEND_TRANSACTION = 10;
DECLINE_REQUEST_TRANSACTION = 11;
Always use protobufs by reference & generate handlers
2023-08-18 11:39:59 +00:00
SYNC_INSTALLATION_CONTACT_V2 = 12;
Add Commands (#1731) This commit adds handling of Transaction commands.
2020-01-10 18:59:01 +00:00
SYNC_INSTALLATION_ACCOUNT = 13;
Add parsing of messages
2020-07-03 08:26:35 +00:00
CONTACT_CODE_ADVERTISEMENT = 15;
PUSH_NOTIFICATION_REGISTRATION = 16;
PUSH_NOTIFICATION_REGISTRATION_RESPONSE = 17;
Add push notification register message
2020-06-30 07:50:59 +00:00
PUSH_NOTIFICATION_QUERY = 18;
Add parsing of messages
2020-07-03 08:26:35 +00:00
PUSH_NOTIFICATION_QUERY_RESPONSE = 19;
PUSH_NOTIFICATION_REQUEST = 20;
PUSH_NOTIFICATION_RESPONSE = 21;
Added emoji reaction app meta message type
2020-07-20 13:17:57 +00:00
EMOJI_REACTION = 22;
group chat invitation
2020-08-07 13:49:37 +00:00
GROUP_CHAT_INVITATION = 23;
Added CHAT_IDENTITY application meta type also make generate
2020-10-28 13:21:29 +00:00
CHAT_IDENTITY = 24;
Handle organisation membership requests
2020-11-18 09:16:51 +00:00
COMMUNITY_DESCRIPTION = 25;
chore: remove community invitations
2023-08-03 19:23:38 +00:00
COMMUNITY_INVITATION = 26 [deprecated=true];
Request/Decline access to communities
2021-01-11 10:32:51 +00:00
COMMUNITY_REQUEST_TO_JOIN = 27;
add PinMessage and PinnedMessage (#2180) * add PinMessage and PinnedMessage * fix gruop pin messages * add SkipGroupMessageWrap to pin messages * update pinMessage ID generation to be symmetric
2021-05-14 21:22:50 +00:00
PIN_MESSAGE = 28;
Separate edit message protocol message
2021-06-07 08:31:27 +00:00
EDIT_MESSAGE = 29;
feat: user status (#2276) * feat: user status * fix: sql filename and null pointer exceptions * fix: lint * refactor: remove StatusUpdate from database.go * fix: adding missing status updates persistence methods * fix: code review * Update version and bindata, and lint * fix: failing test * fix: code review * fix update statement
2021-07-22 17:41:49 +00:00
STATUS_UPDATE = 30;
Delete messages (#2279) * feat: add api and handling to delete messages * fix(delete): add whitelist to message types that can be deleted
2021-07-26 21:06:32 +00:00
DELETE_MESSAGE = 31;
Sync Communities (#2253) * Added community sync protobuf * Updated community sync send logic * Integrated syncCommunity handling * Added synced_at field and tidied up some other logic * persistence testing * Added testing and join functionality * Fixed issue with empty scan params * Finshed persistence tests for new db funcs * Midway debug of description not persisting after sync * Resolved final issues and tidied up * Polish * delint * Fix error not handled on SetPrivateKey * fix infinite loop, again * Added muted option and test fix * Added Muted to syncing functions, not just in persistence * Fix bug introduced with Muted property * Added a couple of notes for future devs * Added most of the sync RequestToJoin functionality Tests need to be completed and tests are giving some errors * Finished tests for getJoinedAndPending * Added note * Resolving lint * Fix of protobuf gen bug * Fixes to community sync tests * Fixes to test * Continued fix of e2e * Final fix to e2e testing * Updated migration position * resolve missing import * Apparently the linter spellchecks * Fix bug from #2276 merge * Bug fix for leaving quirkiness * Addressed superfluous MessengerResponse field * Addressed feedback * VERSION bump
2021-08-06 15:40:23 +00:00
SYNC_INSTALLATION_COMMUNITY = 32;
Anon Metrics Broadcast (#2198) * Protobufs and adapters * Added basic anon metric service and config init * Added fibonacci interval incrementer * Added basic Client.Start func and integrated interval incrementer * Added new processed field to app metrics table * Added id column to app metrics table * Added migration clean up * Added appmetrics GetUnprocessed and SetToProcessedByIDs and tests There was a wierd bug where metrics in the db that did not explicitly insert a value would be NULL, so could not be found by . In addition I've added a new primary id field to the app_metrics table so that updates could be done against very specific metric rows. * Updated adaptors and db to handle proto_id I need a way to distinguish individual metric items from each other so that I can ignore the ones that have been seen before. * Moved incrementer into dedicated file * Resolve incrementer test fail * Finalised the main loop functionality * Implemented delete loop framework * Updated adaptors file name * Added delete loop delay and quit, and tweak on RawMessage gen * Completed delete loop logic * Added DBLock to prevent deletion during mainLoop * Added postgres DB connection, integrated into anonmetrics.Server * Removed proto_id from SQL migration and model * Integrated postgres with Server and updated adaptors * Function name update * Added sample config files for client and server * Fixes and testing for low level e2e * make generate * Fix lint * Fix for receiving an anonMetricBatch not in server mode * Postgres test fixes * Tidy up, make vendor and make generate * delinting * Fixing database tests * Attempted fix of does: cannot open `does' (No such file or directory) not: cannot open `not' (No such file or directory) exist: cannot open `exist' (No such file or directory) error on sql resource loas * Moved all anon metric postgres migration logic and sources into a the protocol/anonmetrics package or sub packages. I don't know if this will fix the does: cannot open `does' (No such file or directory) not: cannot open `not' (No such file or directory) exist: cannot open `exist' (No such file or directory) error that happens in Jenkins but this could work * Lint for the lint god * Why doesn't the linter list all its problems at once? * test tweaks * Fix for wakuV2 change * DB reset change * Fix for postgres db migrations fails * More robust implementation of postgres test setup and teardown * Added block for anon metrics functionality * Version Bump to 0.84.0 * Added test to check anon metrics broadcast is deactivated * Protobufs and adapters * Added basic anon metric service and config init * Added new processed field to app metrics table * Added id column to app metrics table * Added migration clean up * Added appmetrics GetUnprocessed and SetToProcessedByIDs and tests There was a wierd bug where metrics in the db that did not explicitly insert a value would be NULL, so could not be found by . In addition I've added a new primary id field to the app_metrics table so that updates could be done against very specific metric rows. * Updated adaptors and db to handle proto_id I need a way to distinguish individual metric items from each other so that I can ignore the ones that have been seen before. * Added postgres DB connection, integrated into anonmetrics.Server * Removed proto_id from SQL migration and model * Integrated postgres with Server and updated adaptors * Added sample config files for client and server * Fix lint * Fix for receiving an anonMetricBatch not in server mode * Postgres test fixes * Tidy up, make vendor and make generate * Moved all anon metric postgres migration logic and sources into a the protocol/anonmetrics package or sub packages. I don't know if this will fix the does: cannot open `does' (No such file or directory) not: cannot open `not' (No such file or directory) exist: cannot open `exist' (No such file or directory) error that happens in Jenkins but this could work
2021-09-01 12:02:18 +00:00
ANONYMOUS_METRIC_BATCH = 33;
[pairing] Sync chat removing
2021-10-05 17:26:02 +00:00
SYNC_CHAT_REMOVED = 34;
[pairing] Sync read messages
2021-10-12 10:33:32 +00:00
SYNC_CHAT_MESSAGES_READ = 35;
Add backing up of contacts We periodically check whether we should backup contacts through waku. Currently it's not tied to any event, it will only schedule a backup on a tick, or through the provided API endpoint.
2021-10-11 15:39:52 +00:00
BACKUP = 36;
Sync activity center (#2443) sync activity center
2021-12-02 14:23:02 +00:00
SYNC_ACTIVITY_CENTER_READ = 37;
SYNC_ACTIVITY_CENTER_ACCEPTED = 38;
SYNC_ACTIVITY_CENTER_DISMISSED = 39;
Sync bookmarks
2022-01-17 03:42:11 +00:00
SYNC_BOOKMARK = 40;
Sync clear history
2022-02-10 10:00:59 +00:00
SYNC_CLEAR_HISTORY = 41;
Sync Settings (#2478) * Sync Settings * Added valueHandlers and Database singleton Some issues remain, need a way to comparing incoming sql.DB to check if the connection is to a different file or not. Maybe make singleton instance per filename * Added functionality to check the sqlite filename * Refactor of Database.SaveSyncSettings to be used as a handler * Implemented inteface for setting sync protobuf factories * Refactored and completed adhoc send setting sync * Tidying up * Immutability refactor * Refactor settings into dedicated package * Breakout structs * Tidy up * Refactor of bulk settings sync * Bug fixes * Addressing feedback * Fix code dropped during rebase * Fix for db closed * Fix for node config related crashes * Provisional fix for type assertion - issue 2 * Adding robust type assertion checks * Partial fix for null literal db storage and json encoding * Fix for passively handling nil sql.DB, and checking if elem has len and if len is 0 * Added test for preferred name behaviour * Adding saved sync settings to MessengerResponse * Completed granular initial sync and clock from network on save * add Settings to isEmpty * Refactor of protobufs, partially done * Added syncSetting receiver handling, some bug fixes * Fix for sticker packs * Implement inactive flag on sync protobuf factory * Refactor of types and structs * Added SettingField.CanSync functionality * Addressing rebase artifact * Refactor of Setting SELECT queries * Refactor of string return queries * VERSION bump and migration index bump * Deactiveate Sync Settings * Deactiveated preferred_name and send_status_updates Co-authored-by: Andrea Maria Piana <andrea.maria.piana@gmail.com>
2022-03-23 18:47:00 +00:00
SYNC_SETTING = 42;
Always use protobufs by reference & generate handlers
2023-08-18 11:39:59 +00:00
COMMUNITY_MESSAGE_ARCHIVE_MAGNETLINK = 43;
SYNC_PROFILE_PICTURES = 44;
feat: accounts improvements applied - old `accounts` table is moved/mapped to `keypairs` and `keypairs_accounts` - `keycards` table has foreign key which refers to `keypairs.key_uid` - `Keypair` introduced as a new type - api endpoints updated according to this change
2023-05-16 10:48:00 +00:00
SYNC_ACCOUNT = 45;
Initial support for mutual contact requests
2022-01-18 16:31:34 +00:00
ACCEPT_CONTACT_REQUEST = 46;
RETRACT_CONTACT_REQUEST = 47;
refactor: Require request access for all communities This commit introduces a few changes regarding users accessing communities: While the APIs still exist, community invites should no longer be used, instead communities should merely be "shared". Sharing a community to users allows users to "join" the community, which in reality makes them request access to that community. This means, users have to request access to any community, even if the community has permissions set to NO_MEMBERSHIP Only difference between ON_REQUEST and NO_MEMBERSHIP is that ON_REQUEST communities require manual approval of the owner/admin to access a community. NO_MEMBERSHIP communities accept automatically (as soon as owner/admin receives the request). This also implies that users are no longer optimistically added to the member list of communities, but only after they have been accepted. This introduces a bit of a message ping-pong for users to know that someone is now part of a community
2022-07-01 13:54:02 +00:00
COMMUNITY_REQUEST_TO_JOIN_RESPONSE = 48;
feat: sync `CommunitySettings` across paired devices This commit introduces a new `clock` field in the `communities_settings` table so that it can be leveraged for syncing community settings across devices. It alsoe exends existing `syncCommunity` APIs to generate `SyncCommunitySettings` as well, avoiding sending additional sync messages for community settings. When editing communities however, we still sync community settings explicitly are we aren't syncing the community itself in that case.
2022-06-01 07:55:48 +00:00
SYNC_COMMUNITY_SETTINGS = 49;
feat: contact verification request (#2586) fix: add verification request to response fix: code review add missing functions and simplify timestamp usage fix: sync verification requests feat: add endpoint to fetch all received verification requests feat: add signal when trusting verification request Co-authored-by: Jonathan Rainville <rainville.jonathan@gmail.com>
2022-07-05 19:49:44 +00:00
REQUEST_CONTACT_VERIFICATION = 50;
ACCEPT_CONTACT_VERIFICATION = 51;
DECLINE_CONTACT_VERIFICATION = 52;
SYNC_TRUSTED_USER = 53;
SYNC_VERIFICATION_REQUEST = 54;
[#13672] Sync contact request decision
2022-08-07 14:25:03 +00:00
SYNC_CONTACT_REQUEST_DECISION = 56;
feat: introduce and distribute RequestToLeave community closes: #2812
2022-08-22 10:10:31 +00:00
COMMUNITY_REQUEST_TO_LEAVE = 57;
feat: delete for me (#2866)
2022-09-28 11:42:17 +00:00
SYNC_DELETE_FOR_ME_MESSAGE = 58;
feat: sync saved addresses Main changes: - Extend saved addresses DB with sync info: sync timestamp, update timestamp and soft removed flag - Create custom protobuf message payload to sync saved addresses - Cleanup saved addresses on each start of messenger, by deleting soft removed older entries - Sync all saved addresses on Messenger.SyncDevices calls - Sync particular changes to saved addresses - Add SavedAddressManager instance to messenger - Note, can't find a clean way to pass the SavedAddressManager to the messenger, so we create another one - Add tests for sync and new DB API Closes: #7229
2022-09-14 10:46:11 +00:00
SYNC_SAVED_ADDRESS = 59;
feat(communities): Cancel request to join community (#2915)
2022-10-28 08:41:20 +00:00
COMMUNITY_CANCEL_REQUEST_TO_JOIN = 60;
feat(ActivityCenter): Add message for canceling contact requests (#2992) * feat(ActivityCenter): Add message for canceling contact requests * feat(Contacts): GetVerificationRequestSentTo returns last verification request * Fix error message in protocol/messenger_contact_verification.go Co-authored-by: Jonathan Rainville <rainville.jonathan@gmail.com> Co-authored-by: Jonathan Rainville <rainville.jonathan@gmail.com>
2022-12-14 08:27:02 +00:00
CANCEL_CONTACT_VERIFICATION = 61;
feat: accounts improvements applied - old `accounts` table is moved/mapped to `keypairs` and `keypairs_accounts` - `keycards` table has foreign key which refers to `keypairs.key_uid` - `Keypair` introduced as a new type - api endpoints updated according to this change
2023-05-16 10:48:00 +00:00
SYNC_KEYPAIR = 62;
chore: synchronization improvements applied to keycards This is the second step of improvements over keypairs/keycards/accounts. - `SyncKeycardAction` protobuf removed - `SyncKeypair` protobuf is used for syncing keycards state as well as for all keycards related changes - `last_update_clock` column removed from `keypairs` table cause as well as for accounts, any keycard related change is actually a change made on a related keypair, thus a keypair's clock keeps the clock of the last change - `position` column added to `keypairs` table, needed to display keycards in the same order accross devices
2023-07-05 12:41:58 +00:00
SYNC_SOCIAL_LINKS = 63;
SYNC_ENS_USERNAME_DETAIL = 64;
Always use protobufs by reference & generate handlers
2023-08-18 11:39:59 +00:00
SYNC_ACTIVITY_CENTER_NOTIFICATIONS = 65;
chore: synchronization improvements applied to keycards This is the second step of improvements over keypairs/keycards/accounts. - `SyncKeycardAction` protobuf removed - `SyncKeypair` protobuf is used for syncing keycards state as well as for all keycards related changes - `last_update_clock` column removed from `keypairs` table cause as well as for accounts, any keycard related change is actually a change made on a related keypair, thus a keypair's clock keeps the clock of the last change - `position` column added to `keypairs` table, needed to display keycards in the same order accross devices
2023-07-05 12:41:58 +00:00
SYNC_ACTIVITY_CENTER_NOTIFICATION_STATE = 66;
feat: auto re-apply rejected community events closes: status-im/status-desktop#11552
2023-08-08 13:16:29 +00:00
COMMUNITY_EVENTS_MESSAGE = 67;
chore: synchronization improvements applied to keycards This is the second step of improvements over keypairs/keycards/accounts. - `SyncKeycardAction` protobuf removed - `SyncKeypair` protobuf is used for syncing keycards state as well as for all keycards related changes - `last_update_clock` column removed from `keypairs` table cause as well as for accounts, any keycard related change is actually a change made on a related keypair, thus a keypair's clock keeps the clock of the last change - `position` column added to `keypairs` table, needed to display keycards in the same order accross devices
2023-07-05 12:41:58 +00:00
COMMUNITY_EDIT_SHARED_ADDRESSES = 68;
Feat/sync customization color (#3702) * sync customization color * addressed feedback from @cammellos * add param customizationColorClock to function generateOrImportAccount
2023-07-18 13:35:06 +00:00
SYNC_ACCOUNT_CUSTOMIZATION_COLOR = 69;
fix: wallet accounts ordering improvements
2023-07-16 11:11:48 +00:00
SYNC_ACCOUNTS_POSITIONS = 70;
feat: auto re-apply rejected community events closes: status-im/status-desktop#11552
2023-08-08 13:16:29 +00:00
COMMUNITY_EVENTS_MESSAGE_REJECTED = 71;
feat: community privileged user sync message (#3879)
2023-08-15 15:27:01 +00:00
COMMUNITY_PRIVILEGED_USER_SYNC_MESSAGE = 72;
waku2: static shards (#3944) - use protected topics for communities - associate chats to pubsub topics and populate these depending if the chat belongs to a community or not - mailserver functions should be aware of pubsub topics - generate private key for pubsub topic protection when creating a community - add shard cluster and index to communities - setup shards for existing communities - distribute pubsubtopic password - fix: do not send the requests to join and cancel in the protected topic - fix: undefined shard values for backward compatibility - refactor: use shard message in protobuffers
2023-10-12 19:21:49 +00:00
COMMUNITY_SHARD_KEY = 73;
feat(pairing): sync 1-1 chats and groups on pairing devices (#4102) Fixes #3547
2023-10-17 13:24:15 +00:00
SYNC_CHAT = 74;
Handle membership update message This commit does a few things: 1) Handle membership updates using protobuf and adds the relevant endpoints. 2) Store in memory a map of chats + contacts for faster lookups, which are then flushed to disk on each update 3) Validate incoming messages Sorry for the large pr, but you know, v1 :)
2019-12-02 15:34:05 +00:00
}
}