[HTTPS-E Rulesets] Typepad - should be disabled in stable builds?

[Christopher Liu]

To whom it may concern:

This is something I forgot to mention in my last couple of emails, I guess.

I noticed a little while ago that most of the URLs that were covered
by the Typepad ruleset now redirect back to http, for example
http://www.typepad.com/services/toolbar?blog_id=6a0120a85dcdae970b0128776faab5970c&asset_id=6a0120a85dcdae970b016762dec8cb970b&atype=Individual&to=http%3A%2F%2Fwww.codinghorror.com%2Fblog%2F2012%2F02%2Fshould-all-web-traffic-be-encrypted.html&autofollowed=0&safe_to_modify_body=0
(found on http://www.codinghorror.com/blog/2012/02/should-all-web-traffic-be-encrypted.html
).
I then noticed (assuming I am reading
https://gitweb.torproject.org/https-everywhere.git/tree/HEAD:/src/chrome/content/rules
correctly) that the ruleset seems to have been removed entirely from
the mainline/trunk of the repository - for presumably that exact
reason.

Since a 2.0.6 release seems likely, I just want to make sure you will
be disabling/removing the Typepad ruleset in stable builds as well, if
indeed I understood your plans correctly.

C. Liu