[Network Solutions] Add comments
[Network Solutions] Add cms
[Openmoko] Add coverage

And comment.
[Read the Docs.org] Add comments
[RHUL.ac.uk] Add helpdesk.ma

And comments.
RStudio.com
SliTaz.org
SuperStats.com
[symlynX] Change comment

New cert, same behavior.
TAU.ac.il
[The Business Journals] Add coverage
[The Open Group] Add coverage
[Tumblr] Add coverage
[tvsupport.net] Add help
Upworthy.com
[VideoLAN] Re-add git

And update (remove) comment.
[Zareason.com] Cosmetics
Merge remote-tracking branch 'origin/master'
These two functions simply return on HTTPS urls.

Remove the null HTTPS listeners, which significantly slows down
browsing as Chromium has to always invoke this extension.

Signed-off-by: Nick Semenkovich <semenko@alum.mit.edu>
The function "potentiallyApplicableRulesets" is hot, and its results are stable.

From profiling, this is *very* slow, and it's easy to see why. The calls look like:

     Loading www.nytimes.com ->
          Load every image (20+ images at graphics8.nytimes.com)
	       Call potentiallyApplicableRulesets every time
	       	    Return the same result every time :(

Let's use a simple LRU cache to store those results.

This adds the MIT-licensed LRU cache from: https://github.com/rsms/js-lru

The cache isn't persistent (it's in memory, not LocalStorage or elsewhere),
so we don't have to worry about stale data when the extension updates.

Signed-off-by: Nick Semenkovich <semenko@alum.mit.edu>