Suggestion: Whitelist timeout option

[GoogleCodeExporter]

When https-finder finds a site with an https version, but it is not 
satisfactory, we add it to the whitelist... but as time goes by, more and more 
sites makes a satisfactory https version of them, so a site that today is not 
satisfactory could be so tomorrow.

My suggestion is to add an option for the sites in the whitelists to get out of 
the list automatically after a predefined time, adjustable by the user.

Original issue reported on code.google.com by strel...@gmail.com on 18 Dec 2011 at 8:00

[GoogleCodeExporter]

Are you referring to the permanent whitelist? 

Currently, if you click "Not now" to an alert, or if a site does not have valid 
HTTPS, we whitelist it until the next time the browser restarts (or until the 
user clicks Clear Whitelist manually). 

Seems like a timeout on the permanent whitelist would just get annoying and 
possible come across as a bug (if whitelisted items keep getting removed 
without any user interaction).

Original comment by jacobsK...@gmail.com on 18 Dec 2011 at 8:42

[GoogleCodeExporter]

Yes, the permanent whitelist... my suggestion is about the timeout as an 
option, maybe not in the options dialog but in about:config and disabled by 
default, but for the user to able to add a site with an unsatisfactory https 
version, for let's say some months, or a year or two, then being removed from 
list automatically for https-finder to trigger again alerts for that site if 
visited, so the user is able to check if a previously rejected site now has a 
satisfactory https version, after that "quarantine" period he has defined.
But it's just a suggestion...

Original comment by strel...@gmail.com on 19 Dec 2011 at 2:34