Kill Your TV:
> The I2P project recently revamped its site and switched to a new
> domain. This branch updates the URLs to reflect the new domain and also
> switches the ports list to a simple list instead of a table to
> address the following comment.
> 
>> * regarding commit c32cab5 ("I2P: Document ferm exceptions"):  the
>>   HTML table seems a bit too much markup for me; how about just using
>>   a simple list? (not a blocker either, just nitpicking probably ;)

Fine with me.

> The branch is at
> http://repo.or.cz/w/tails/kytv.git/shortlog/refs/heads/bugfix/new-i2p-site

I see in commit 537285f that you also changed the IP2 eepsite to
http://i2p-projekt.i2p. It this different address recommended over
http://www.i2p2.i2p? Because if it is the case then we should also
update the bookmarks in
config/chroot_local-includes/etc/iceweasel/profile/bookmarks.html.

I'll wait for your answer before merging that.

See:

+++ b/wiki/src/doc/anonymous_internet/i2p.mdwn
@@ -1,6 +1,6 @@
 [[!meta title="Using I2P"]]

-[I2P](http://www.i2p2.de/) is an alternative anonymity network to Tor
+[I2P](https://geti2p.net/) is an alternative anonymity network to Tor
 which supports most common Internet activities like web browsing,
 email, filesharing etc. Unlike Tor, whose main focus arguably is on
 accessing sites from the "normal" Internet, I2P is more oriented
@@ -9,7 +9,7 @@ towards being a closed [[!wikipedia darknet]], separate
from the
 so called Eepsite, that is only accessible within I2P using the `.i2p`
 top level domain (similar to `.onion` for Tor hidden services). For
 instance, the I2P homepage can also be accessed through I2P via
-<http://www.i2p2.i2p>.
+<http://i2p-projekt.i2p>.

 I2P is not started by default in Tails, but can be started manually
 throught the menu:


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
tails-dev mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
[email protected].

Reply via email to