This repository has been archived by the owner on Jan 10, 2025. It is now read-only.
local backup v2 #20
Closed
local backup v2 #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Upstream molly tags
Fix Verify Device
Add missing summaries
In minified builds
Fix typo in user-facing strings
Use new RemoteMessage constructor
If needed : when switching notification method or when UnifiedPush status changes. Always use UnifiedPushRefreshJob to update UP related component and to register to MollySocket.
on MainActivity. This could occur if the Distributor unregister Molly or if the distributor has been uninstalled
Fix foreground service not correctly stopped with air gapped
|
Another option would be to use signal free tier for the messages and local storage for the medias |
valldrac
force-pushed
the
main
branch
3 times, most recently
from
3d1e55e to
6ca620d
Compare
This was referenced Nov 18, 2024
valldrac
force-pushed
the
main
branch
2 times, most recently
from
6aa5046 to
3ca7d89
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea is to use the backup v2 mechanism in a folder so any cloud management can sync this folder, and they won't have to send the same attachments over and over.
The message archive have to be overridden, and will override the remote one too. They probably do the message archive server side, I've not yet checked. There is a function to upload the message archive (org.thoughtcrime.securesms.backup.v2.BackupRepository#uploadBackupFile) but this is only used in the internal playground. This could still be run from time to time (like the current backup - v1)
If the user use
Signal/Backupsfor their backups we can do:Signal/Backups/v2/messages.bak
Signal/Backups/v2/m/aa/aaarandom // Which is one encrypted attachment
Signal/Backups/v2/m/ba/baarandom // another encrypted
The next backup will have to send
Signal/Backups/v2/messages.bak // Which is overridden
Signal/Backups/v2/m/az/azxrandom // new attachment