concerned_citizen

I know this is easy to forget, but Google is tens of thousands of people and doesn't act with one mind. The people who created End-to-End aren't the same people that would necessarily, e.g., add encryption to Hangouts.

Typically the "JavaScript" in that consensus really means JavaScript running on an everday webpage. For example, it wouldn't really apply to using encryption in JS under Node. Nor does it really apply to JS running in an extension in Chrome.

It is not feasible with the current design of Greasemonkey. The Greasemonkey script and the page's own script share access to the DOM. It is very difficult to prevent the page's script from observing the changes that the Greasemonkey script makes.

I could imagine there could be some alternate design for a Greasemonkey-like extension that would allow this. The concept would be that this Greasemonkey2 would add a layer on top of a web page. The script inside this layer could observe what happened in a web page, but not change it. Then it could make modifications to its own layer as it saw fit.

I'm not the creator, that's Aaron Boodman, and he works for Google now and no longer contributes. But the name is a play on the name of the Firefox JavaScript engine: Spidermonkey.

Actually, it was a reference to the slang term 'grease monkey', for an auto mechanic.

Source: I'm Aaron Boodman, I named it. I think there might have also been a nod toward Spidermonkey, but I can't remember for sure.

Briefly I think a good place to start would be to understand how Greasemonkey works. Perhaps you could do that by contributing a few bugfixes to it.