Complete de-obfuscation of existing codebase.

[tgxn]

I have noticed that most of the codebase here is still using obfuscated variable/function names within it's source files.

This is a concern to me as the codebase is still not fully understood and is not maintainable in this format.

I am wondering if there is a driver to have this fully de-obfuscated and bring the project in-line with current naming and formatting standards for JavaScript projects so that it can be maintained going forward.

If this is something that would be beneficial to this project, I am willing to put some time into this process.

[tgxn]

I've just noticed there is a more deobfuscated branch of this, further to this, is there a reason this has not been merged into master with a matching folder structure?

[EranSch]

Hey @tgxn, very astute of you!

The origin of that branch was an effort of mine to essentially rewrite the entire extension, manually deobfuscating and enhancing where I could.

The original push to undertake this endeavor was a takedown from the Chrome webstore (See #13). After enough nudging, I began the rewrit however after making some progress (as you see in the referenced branch) I was able to get a human on the Chrome team to review of the source to verify that there wasn't anything nefarious. Once the extension was re-published, the rewrite fell swiftly off my list.

I love the idea of re-building this tool in order to keep it open source and maintainable. If you're up for contributing, I would definitely welcome it!

[EranSch]

I don't recall why I altered the folder structure but ultimately the goal of mine was to restructure the project to support using ES2015 and ES Modules along with a Babel build/bundle process. Then update the Travis CI config to handle all of that for the production releases.

[EranSch]

Tagging this with "Help wanted" in case anyone out there wants to help out.