Selective Data Sync for Secondary Devices [either all or just recent history]

[imysl0]

When adding a second device, we propose to offer users the option to select the scope of data synchronization. Beyond the essential account authentication information, users should be able to choose whether to sync chat history and files, or to sync only data from the most recent few days.

Expected behavior

When a user adds a second device, the system displays a friendly setup interface that allows users to easily select the scope of data synchronization. In addition to automatically syncing basic account authentication information (such as login status), users can check options to decide whether to sync complete chat history and files, or set it to only sync data from recent days. This way, users can manage cross-device synchronization more flexibly, saving storage space and protecting privacy.

Actual behavior

Currently, when adding a second device, the system typically syncs all data by default (including all chat history and files), and users have no option to customize the sync scope. This may cause device storage to fill up quickly, or inadvertently sync unnecessary sensitive information, affecting user experience and data security.

[imysl0]

When my account is very large (with lots of history records and files), adding a second device also takes a very long time. If the sync scope were selectable, I think the speed would be much faster. Sometimes, files and old messages don’t really need to be synced

[bencan]

Closely related to your proposal (as backup files can also be used to add second devices) I suggested here letting people make lightweight backups that do not include chat histories and files, which will make the process much faster and also not use so much storage on the backup media:

@bencan

Having some kind of checkbox asking the user if they want to backup account chats as well as account credentials and contacts, or just account credentials and contacts

@bencan

Hopefully the backup feature will in future make it optional to include the chat messages, so it will be possible to make lightweight backups with minimal file size.

I think it makes sense to let people choose to limit the scope of data sync and also to limit the scope of backups and I suspect that these are two sides of the same coin which could be addressed together.

[ian]

Also related:

Delta chat id backup?

You can use the export backup feature already implemented. If you find the file too large to handle, you need to prune the zip manually. You can remove past messages, xdc state updates, attachments, but not your avatar and then vacuum the database file with a few SQL commands.

[imysl0]

You’re right. I think it’s the same thing.

[imysl0]

The method mentioned in the post is actually a great detour to get it done.
Of course, it would be better if there were a more direct way