- 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.
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...
Sometimes the mtn syncs hang until aborted. Well, my syncing with welterde and
echelon would hang periodically until I added the same timeout support I'm
adding here. In short, if Montone's action has not completed within 20 minutes,
forcably kill the process. /usr/bin/timeout is a part of coreutils so most
(all?) Linux distributions should have it but I don't require timeout to exist.
If "timeout" can be found, it'll be used.
Also, set site-updater.sh to change to the directory in which the script is
located. This way one can give an absolute path in a cronjob.
Both of these changes should be low risk.
The Mailman instance at lists.i2p2.(de|i2p) was set up by Meeh and I in 2013
and is accessible via both I2P and the internet with newly set-up SSL certs.
