Introduce a better mechanism to avoid overriding the synced user database

[kelsos]

Problem Definition

The current implementation erroneously assumes that the database size is always increasing and that a new database will be always bigger.

Unfortunately this assumption is wrong since a user database can become smaller due to data purging, vacuuming etc. Since this assumption is wrong, this requires users to manually intervene often so that premium sync functionality remains uninterrupted.

The mechanism above, was introduced so that users that sync between two devices won't overwrite their remotely synced databases by accident.

A user that uses a single machine should never have to manually intervene in order for sync to resume, so we need to update the mechanism/logic in a way that still prevents accidental overwrite without blocking the sync process unnecessarily for users that are only using a single device

Introducing metadata about the syncing device might help to resolve this problem.

[Dozie2001]

Hey @kelsos can I get assigned to this? plus ask some questions

[kelsos]

Hey @Dozie2001, thanks. Unfortunately this will have to be picked up by someone from the team since it also will most certainly require changes to parts of our infrastructure, and that is something only the team has access to.

[Dozie2001]

Are there other issues open to contributors. Would be nice if you guys had a good first issues

[kelsos]

Are there other issues open to contributors. Would be nice if you guys had a good first issues

there is a good first issue tag if you search and it has 4 items currently.