Rated 4 out of 5 stars

Supports HTTPS pages. Utilizes inline translation. It could be better if it also allowed translations of highlighted text, a la gTranslate, and if it displayed which languages are being translated from.

Rated 4 out of 5 stars

Blocks DNS queries, redirects, in-page content, and searches, but has an infinite unstoppable page load when trying to search a banned term from within a search engine (tested on Google). Needs an icon for faster access. When blocking pages that refresh content, there should be an option to disable multiple messages for the same site. Perhaps add a quick option to whitelist or blacklist a page after going to it that doesn't require copy/paste (like clicking on an icon and choosing blacklist or whitelist, perhaps based on the what BlockSite Plus is currently being used as). Overall a good extension that could use some work.

Rated 1 out of 5 stars

This is an amazing add-on, but I am rating it 1 out of 5 stars because: it doesn't automatically apply the changes before displaying the webpage making it completely unusable at night (versus the way Stylish forces changes before load, thus stopping websites from flashing white before the color is changed), it really needs a blacklist when a global color scheme is set (I don't want it to show on cert error pages) and it makes page hang while loading a new page more noticeable because it takes longer to load pages. Perhaps you (developer) could make Color Transform save changes to Stylish?

FixRated 4 out of 5 stars

Another way to fix SSL functionality is just to change http://images.google.com to http://www.google.com because Google supports encryption for regular Google URL's and not the images.google.com subdomain. (Links are redirected to SSL normally for those who choose to use it, otherwise HTTP is used in my proposed fix). Tested this myself with your add-on and it works, although it is slower than just using SSL by default. Cheers.

Edit: Or those of you who use SSL with this extension could just change your redirection rules... ( http://images.google.com/* to https://encrypted.google.com/* )

Edit 2: You (developer) could always make a separate extension for HTTPS and avoid all of this hassle.