Describe the problem
Right now when you start using Sable on multiple devices or different instances, you have to configure each one manually and nothing is shared between them besides profile things like bio and such.
Describe the solution you'd like
Add a versioned im.sable.settings key in account data to be able to persistent the settings across all devices running sable for a unified and seamless experience.
Note, we should avoid syncing things like telemetry or anything that has potential for abuse, since we don't have control over what other actors might do to im.sable.settings. Also have a good invalidation system in case the key data is invalid.
Alternatives considered
No response
Additional context
No response
Describe the problem
Right now when you start using Sable on multiple devices or different instances, you have to configure each one manually and nothing is shared between them besides profile things like bio and such.
Describe the solution you'd like
Add a versioned
im.sable.settingskey in account data to be able to persistent the settings across all devices running sable for a unified and seamless experience.Note, we should avoid syncing things like telemetry or anything that has potential for abuse, since we don't have control over what other actors might do to
im.sable.settings. Also have a good invalidation system in case the key data is invalid.Alternatives considered
No response
Additional context
No response