mylainos

A lot of features won't work with WE because we can't change the settings anymore. Should we rewrite everything to WE or should we progressively move part of the extension...

Here the list of features of RAS and the compatibility with WE. When something won't work it will be marked like this: **Won't work** ~~Feature~~ A tick mean it's sure...

And Self-Destructing Cookies also need to be rewrite to WE.

> 4. We should lay down a plan about the future of this "tool to help prevent browser fingerprinting". I think the extension should be updated on AMO and we...

RAS use the addon sdk and Firefox 57 will execute only WebExtensions. This addon need a rewrite and it will be multiprocess compatible (as every WebExtensions).

If @dillbyrne is ok we will merge it when it's ready.

`require('chrome')` is used for messages between windows and for intercept request in order to change the User Agent, the headers, etc. [WebRequest API](https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest) allow to rewrite the request and it's...

It's because I've merge the webext branch to the master branch. https://github.com/Mylainos/random-agent-spoofer/

So there is no community effort for now to rewrite RAS as a webext ? Because I'm starting to do it ;) This is just the beginning, nothing works.

I know that the access to preferences are not supported by the Chrome API's but there is way to change that, [WebExtensions Experiments](https://webextensions-experiments.readthedocs.io/en/latest/index.html). The login WebExtensions Experiments implement browser.login, so...