rokejulianlockhart
rokejulianlockhart написал(а):@serega_da, your phrasal isn’t comprehensible to me. Consequently, are you, summarily, stating that the preferences are, currently, stored in the local browser storage, but should be stored in the server, because they’re so small?
If you want to take the discussion in a different direction, then I agree, let’s discuss our sizes.
On a nearby forum, users ask for synchronization and storage of Bookmarks and History on the server. In six months. And they don’t understand that the size of these files can easily reach 50 MB per user. This can be easily calculated, but of course, no one does this and no one wants to. But there is always enough discussion.
serega_da
I said “small” because BW settings are created using the JSON type - key: value. Their size is minimal. And it cannot create a load on the server.
This topic is already 7 years old. No movement.
This is a complete post, and once again expresses the desire of all its participants.
We’re talking about UI, not secret information. It’s even simpler and doesn’t require transmission protection.
There is a Visual bookmarks - Microsoft Edge Addons
Its author was able to realize this idea. The one here is from 2019.
Its extension stores all settings. And not even on your own server. In Edge it is stored on the MS server. In Chrome, it is stored on a Google server. On someone else’s server, and everything works.
About 50 settings are saved during a clean installation on a clean OS, including custom CSS.
------------
serega_da
As users expressed here and in other feature requests, some settings shouldn’t be forcibly synced, best way to implement a “sync” would be an option where the clients (the different BW apps) could override every “centrally and synced setting” so that it would still be possible to have different settings in the BW apps, if needed.
There were also some suggestions, to have separate sets of settings for the different BW apps, like e.g. in this post.
This topic is 7 years old, even the simplest option “All settings” is not implemented.
There is no need to create any mechanisms for selecting settings options without having the simplest option.
It’s a little fun for developers to read sentences like this: the user must manually select settings for a computer, a touchscreen laptop, a phone.
It’s funny because even in simple CSS, everything has already been done before us:
The @media and new @support directives allow to write COMMON code for all types of devices.
The device should not override the settings. The code itself decides on which device it will work.
The W3C has already taken care of this. And this simple markup language can itself understand what device the user has in front of his eyes.
You created a problem, highlighted it in red, scared users that everything is complicated and implementation is still very far away.
Link
