Synced storage and minor tweaks

[ghost]

Use chrome's synced storage for the redirect url. Also, use a chrome "event page" instead of a background page and use https to access the proxy database.

[tom5760]

Wow, thanks for the updates! I'll take a closer look later tomorrow, but I'll certainly merge this. I'd list you as a contributor in the README and on the Chrome store page, ok?

[ghost]

No problem, hopefully everything looks OK. Thanks for making this great extension! The contributor thing sounds fine, feel free to handle it however you want; I don't have any strong feelings on the subject.

[tom5760]

Two comments:

• Can you add a onChanged listener for sync events? Then the selected proxy would change on all of a user's devices at once, without having to restart the extension or anything.
• Does anything bad happen if using chrome.storage.sync when not logged into Chrome?

[ghost]

• If I'm interpreting the docs correctly, I don't think the onChanged listener is needed. The storage.get call should always return the latest data, i.e. a sync will override the current value. It seems like the onChanged listener is primarily to help update UI or such whenever a change occurs.
• I think chrome.storage.sync should always be fine, the chrome.storage page says When Chrome is offline, Chrome stores the data locally. The next time the browser is online, Chrome syncs the data. Even if a user disables syncing, storage.sync will still work. In this case, it will behave identically to storage.local.

[tom5760]

Ah, I didn't realize that the get was done on each transform. That works. I just tried it and the syncing seems to work well.