[Feature Request]: Synchronization of Watch History and Progress Across Multiple FreeTube Instances

[guillermodotn]

Guidelines

• I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
• I have searched the documentation for information that matches the description of the feature request I want to file, without success.
• This issue contains only one feature request.

Problem Description

To enhance user experience for those utilizing FreeTube on multiple devices, I propose implementing a feature that synchronizes watch history and progress across different FreeTube instances.

Proposed Solution

This can be achieved by leveraging Git, a distributed version control system, to manage and synchronize the relevant data.

Implementation Steps:

1. Private Repository Setup:
   Users create a private repository on a Git hosting service of their choice, such as:

   • GitHub
   • GitLab
   • Gitea
   • ...

2. Data Pull on Startup:
   Upon launching FreeTube, the application pulls the latest data from the user's designated repository to update watch history and progress.

3. Data Push on Exit or Triggered Action:
   When closing FreeTube or upon a user-initiated action, the application commits any changes to the watch history or progress and pushes these updates to the repository.

Advantages:

• No Need for Additional Infrastructure:
  This approach eliminates the requirement for new authentication systems or user management infrastructure, as it utilizes existing Git platforms.

• Alignment with FreeTube's Principles:
  By adopting this method, FreeTube continues to uphold its commitment to customization, privacy, and user freedom.

Alternatives Considered

Currently, users can manually export their watch history from one FreeTube instance and import it into another. This process involves exporting the history file from the source device and importing it on the target device via the application's settings.

Issue Labels

new optional setting, new feature, ease of use improvement

Additional Information

This proposal is inspired by practices used to synchronize configuration files (dot-files) across multiple systems, where Git repositories are employed to maintain consistency and version control.