[backups] splitted JSON instead of big JSON

[jlmxyz]

As a user, I use tab session manager on several devices, at home, at work, on chrome, firefox, chromium... backups are shared on sshfs
in order to manage all saved sessions, I would like instead of a big archive "2021-02-18 22-27-02 (35 sessions).json" I would like to have 35 Json files with a name of session_name.tags.json since I tag all my sessions with "Save device name to session" feature

[perXautomatik]

i like the idea of some sort of alternative system to the "large" jsonfile, (my files are in the size of a 1000+) and was looking into ways to use etl to migrate the sessions into a sql db,

[sienori]

I have implemented incremental backup! 72da718

• One session is saved in one json file.
• When a session is updated, the json file is overwritten.
• Autosave sessions are saved in a separate folder.
• The file name is date - session_name #tags [session_id].json.

This allows you to manage backup sessions individually.
Only updated sessions are saved, saving storage.

[candrapersada]

why when checked, backup can't ignore to choose where to save files manually, for chromium based browsers?

[candrapersada]

I have implemented incremental backup! 72da718

• One session is saved in one json file.
• When a session is updated, the json file is overwritten.
• Autosave sessions are saved in a separate folder.
• The file name is date - session_name #tags [session_id].json.

This allows you to manage backup sessions individually.
Only updated sessions are saved, saving storage.

is there a feature to automatically import/restore from

?