Here is my situation: I have written a number of Chrome userscripts for my personal use. Previously, I only had one machine with one instance of Chrome on it, so I was perfectly happy to dump any persistent data into localStorage.
However, I now have multiple machines, and want to use my userscripts on Chrome on all the machines, with my persistent data coming along for the ride. Synchronizing the userscript code itself is straightforward if a bit tedious (stick it in a Bitbucket repo, then pull and manually install), but I have no idea how to synchronize my localStorage data across machines.
I have considered converting my userscripts to proper Chrome extensions and using the chrome.storage API (data stored using chrome.storage.sync apparently can be sync'd if you have a Google account connected to your Chrome instances, which I do). However, here is the issue with that for my use case:
So: is there some way for me to either 1.) sync localStorage across machines directly, or 2.) use the chrome.storage.sync API without a publically published Chrome extension?
This doesn't really answer the question as I originally asked it, but this is what I ended up doing to solve the problem described above, so whatever.
"unlimitedStorage"
permission in the extension manifest. PouchDB's storage model is significantly superior to the chrome.storage storage model in basically every way (free revision tracking, a documented sync protocol rather than whatever voodoo chrome.storage.sync does, etc.), and the downsides (an extra dependency, need for a separate remote server [see below], etc.) were not a huge issue for me.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.