feature: store customizations in configurable path/file about deluminate

[abstiles]

Good idea. I don't think Google lets Chrome extensions scan the filesystem arbitrarily, but there may be a way to explicitly save/load files with a user action. Would that satisfy you?

[keen99]

yep, certainly better than nothing! (now, can I cron that... ;)

On Tue, Jul 8, 2014 at 11:17 AM, abstiles [email protected] wrote:

Good idea. I don't think Google lets Chrome extensions scan the filesystem
arbitrarily, but there may be a way to explicitly save/load files with a
user action. Would that satisfy you?

Reply to this email directly or view it on GitHub
#27 (comment).

[abstiles]

I would still like to implement this request, but I still cannot find a good way to load an existing file. Still, implementing the relatively recent chrome.storage API would resolve the issue that prompted this request (syncing settings between systems). I'll add that to my priorities list.

[keen99]

for chrome, is the current config stored in a file on the filesystem currently? or tucked away somewhere hard to reach? (looking to recover one from backups...)

[abstiles]

This should be stored somewhere in the filesystem. It's kind of OS dependent, but it should be in a hidden folder in your home directory. You'd have to dig through it a bit to find out where it might be, then restore the folder associated with this extension.

[michaelmior]

Instead, couldn't this just use chrome.storage? This gives 100KB of data which should be more than enough. I assume this was what was mentioned in #62.

[fenollp]

Here's how uBlock Origin uses that storage + how it works on Firefox & some insights that seem valuable https://github.com/gorhill/uBlock/wiki/Cloud-storage

cc #603