- 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...
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.
- Add psi to team for backup news
- Add Android requirements and warning to download page
- Android 0.9.10
- Specs:
More delivery instruction fixups
For consistency, make all the definition sections use <pre> not {% highlight %}
* Add Hebrew language flag (the flag of Israel)
* Update the language list (lang.html.full) to include Hebrew
* Use POT as a basis for yet untranslated files, instead of the Russian
translation files; this should also ensure Transifex doesn't report 100%
translations for these files, instead of 0%
* Update Hebrew translation of priority.po
