Is your feature request related to a problem? Please describe.
I'd like to use multiple Inviduous instances and randomize selection every time a link is opened. There are browser extensions like Privacy-Redirect which automate this. Unfortunately, the user data (settings, subscriptions, playlists) is stored by the individual instances and requires manual export as JSON followed by re-import on the other instance. This is cumbersome in practice and prevents account sharing between instances.
Describe the solution you'd like
Option A) Allow users to run some lean server component that centrally stores their profile data (self-hosted). The instances would then pull the data from the central component.
Option B) Allow users to authorize instances to automatically synchronize the data of that specific user with a number of other instances. For that, the user would have to generate tokens on each instance and share the tokens with all other instances.
The latter is probably an easier solution from a user experience perspective (no self-hosting required by the user).
Describe alternatives you've considered
A) Only use one instance
B) Write a client-side script that regularly pulls profile data from all instances, merges it, and re-imports it into all instances
Additional context
N/A
Is your feature request related to a problem? Please describe.
I'd like to use multiple Inviduous instances and randomize selection every time a link is opened. There are browser extensions like Privacy-Redirect which automate this. Unfortunately, the user data (settings, subscriptions, playlists) is stored by the individual instances and requires manual export as JSON followed by re-import on the other instance. This is cumbersome in practice and prevents account sharing between instances.
Describe the solution you'd like
Option A) Allow users to run some lean server component that centrally stores their profile data (self-hosted). The instances would then pull the data from the central component.
Option B) Allow users to authorize instances to automatically synchronize the data of that specific user with a number of other instances. For that, the user would have to generate tokens on each instance and share the tokens with all other instances.
The latter is probably an easier solution from a user experience perspective (no self-hosting required by the user).
Describe alternatives you've considered
A) Only use one instance
B) Write a client-side script that regularly pulls profile data from all instances, merges it, and re-imports it into all instances
Additional context
N/A