Skip to content

DBR - 5 - Config message handling #451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

mpretty-cyro
Copy link
Collaborator

  • Added logic to handle config messages received via PNs
  • Added code to handle invitations, promotions and kicked messages for groups
  • Added code to fallback to writing a message to disk and showing no notification (means the main app gets content without notifications quicker)
  • Added a work-around for an issue where PNs don't include the namespace value for messages sent to revokedRetrievableGroupMessages
  • Updated the code to retrieve the current users profile from libSession instead of the database (in most places)
  • Updated the code to subscribe for all user config message changes (to better handle updates via PNs)
  • Removed duplicated code
  • Removed remaining database logic from notification extension
  • Fixed an issue with loading the disappearing messages config from a group

This is based on #450

@mpretty-cyro mpretty-cyro self-assigned this May 13, 2025
@mpretty-cyro mpretty-cyro added enhancement New feature or request Jira This ticket is being tracked in Jira labels May 13, 2025
@mpretty-cyro mpretty-cyro force-pushed the feature/dbr5-config-message-handling branch from 320355b to ce5fd3c Compare May 30, 2025 04:26
@mpretty-cyro mpretty-cyro requested a review from RyanRory May 30, 2025 04:29
• Updated the General cache to include the users seckey (rather than fetching it from the DB every time causing unneeded load)
• Updated a bunch of Crypto usage to no longer need a `db` or `dependencies` instance passed to it
• Added unit tests for General.Cache
• Replaced `Identity.userExists` with `General.Cache.userExists` (no need for database access anymore)
• Moved the SwarmPoller message handling logic into it's own function to make debugging stack traces a little easier
• Cleaned up some hard-to-read logic
• Added the new MessageDeduplication table
• Added a migration to populate the MessageDeduplication table
• Added ExtensionHelper functions to store records in the AppGroup for deduplication purposes
• Updated the logic to use MessageDeduplication table & files for deduplication purposes
• Refactored message parsing to not rely on the database
• Refactored message deduplication to not rely on the database in the PN extension
• Removed the old ControlMessageProcessRecord table
• Added logic to handle config messages received via PNs
• Updated the code to subscribe for all user config message changes (to better handle updates via PNs)
• Fixed an issue with loading the disappearing messages config from a group
…weaks

• Added code to handle invitations, promotions and kicked messages for groups
• Added code to fallback to writing a message to disk and showing no notification (means the main app gets content without notifications quicker)
• Added a work-around for an issue where PNs don't include the namespace value for messages sent to `revokedRetrievableGroupMessages`
• Updated the code to retrieve the current users profile from libSession instead of the database (in most places)
• Removed duplicated code
• Removed remaining database logic from notification extension
@mpretty-cyro mpretty-cyro force-pushed the feature/dbr5-config-message-handling branch from ce5fd3c to 70d297b Compare May 30, 2025 05:27
@mpretty-cyro mpretty-cyro merged commit 641bb39 into session-foundation:feature/database-relocation Jun 2, 2025
1 check failed
@mpretty-cyro mpretty-cyro deleted the feature/dbr5-config-message-handling branch June 2, 2025 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Jira This ticket is being tracked in Jira
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants