diff --git a/i2p2www/pages/global/nav.html b/i2p2www/pages/global/nav.html index 5d7f5b88..a27d32d4 100644 --- a/i2p2www/pages/global/nav.html +++ b/i2p2www/pages/global/nav.html @@ -11,7 +11,6 @@
  • {{ _('FAQ') }}
  • {{ _('Applications') }}
    +

    Is it possible to block I2P?

    +

    {% trans %}Yes, by far the easiest and most common way is by blocking bootstrap, or "Reseed" servers. Completely blocking all obfuscated traffic +would work as well (although it would break many, many other things that are not I2P and most are not willing to go this far). +In the case of reseed blocking, there is a reseed bundle on Github, blocking it will also block Github. +You can reseed over a proxy (many can be found on Internet if you do not want to use Tor) or share reseed bundles on a friend-to-friend basis offline.{% endtrans %}

    +

    Getting Started

    @@ -230,6 +259,22 @@ Weechat users can use the following command to add a new network: Click on the Website link at the top of your router console for instructions. {%- endtrans %}

    +

    {% trans %}If I host a website at I2P at home, containing only HTML and CSS, is it dangerous?{% endtrans %}

    +

    {% trans %}If you're hosting a personal blog or doing something otherwise non-sensitive, then you are obviously in little danger. +If you have privacy needs that are basically non-specific, you are in little danger. If you are hosting something sensitive, then +your services will go down at the same time that your router goes down. Someone who observes your downtime and correlates it to +real-world events could probably de-anonymize you with enough effort. I2P has defenses available against this like multihoming or +Tahoe-LAFS, but they require additional set up and are only appropriate for some threat models. There is no magic solution, protecting +yourself from a real threat will take real consideration in any case.{% endtrans %}

    + +

    {% trans %}How Does I2P find ".i2p" websites? {% endtrans %}

    +

    The I2P Addressbook application maps human-readable names to long-term destinations, associated with services, making it more like a hosts file or a contact list than a network database or a DNS service. It's also local-first there is no recognized global namespace, you decide what any given .i2p domain maps to in the end. The middle-ground is something called a "Jump Service" which provides a human-readable name by redirecting you to a page where you will be asked "Do you give the I2P router permission to call $SITE_CRYPTO_KEY the name $SITE_NAME.i2p" or something to that effect. Once it's in your addressbook, you can generate your own jump URL's to help share the site with others.

    + +

    {% trans %}How do I add addresses to the Addressbook? {% endtrans %}

    +

    {% trans %}You cannot add an address without knowing at least the base32 or base64 of the site you want to visit. The "hostname" which is human-readable is only an alias for the cryptographic address, which corresponds to the base32 or base64. Without the cryptographic address, there is no way to access an I2P site, this is by design. Distributing the address to people who do not know it yet is usually the responsibility of the Jump service provider. Visiting an I2P site which is unknown will trigger the use of a Jump service. stats.i2p is the most reliable Jump service.{% endtrans %}

    + +

    {% trans %}If you're hosting a site via i2ptunnel, then it won't have a registration with a jump service yet. To give it a URL locally, then visit the configuration page and click the button that says "Add to Local Addressbook." Then go to http://127.0.0.1:7657/dns to look up the addresshelper URL and share it.{% endtrans %}

    +

    {% trans %}What ports does I2P use?{% endtrans %}