This should prevent some application servers from continuously spamming the
logs in the event that TOUCHFILE can't be found.

     and 'ee9e0c6e682353822ba0ae099de649cd048cd720'

NTCP fix broken date in header
NTCP check connection disable

Add transport idle timeout info
More SSU key clarification

 - the real domain is now geti2p.net
 - the configured cert for i2p2.de is for geti2p.net

Since we have the certificates for i2p2.de we should use them, but since
i2p2.de redirects to geti2p.net anyway, should it really be listed as a
mirror? In any case, it doesn't belong in the "secure" column.

http://geti2p.com is back up and now redirects to https://geti2p.com

     and 'd006fbaf9ad4d208781c95c9de7d9a64ed7cb2c6'

It is currently 302 redirecting to https but it's not available.

Links: More naming of 0x90, by request

add old mailing list links to how page

     and '5e6f4b398fd1877b8d49802fb93e3e050056b2bd'

RE: flattr: Since we force https on the internet facing site, with the http
link there was a warning from the browser about 'mixed mode content' . Using
https://api.flattr.com/button/button-static-50x60.png caused the image to
disappear if one only accepts strong ciphers in the browser
(e.g.  security.tls.version.min set to 2 in Firefox). It would look like
we were doing something wrong even though it's not us, so that's not a viable option.

Looking over https://flattr.com/terms it seems that there's no problem with our
hosting it ourselves. It's also a tiny image besides.

Now to email flattr to strengthen the crypto on their site...

The file sizes are also smaller which should help some with page load times.

(suggested in a post on zzz.i2p)