diff --git a/i2p2www/pages/site/misc/clt.html b/i2p2www/pages/site/misc/clt.html index 9a529f74..f6d99154 100644 --- a/i2p2www/pages/site/misc/clt.html +++ b/i2p2www/pages/site/misc/clt.html @@ -1,13 +1,12 @@ {% extends "global/layout.html" %} {% block title %}I2P at CLT and PetCon 2009.1{% endblock %} -{% block content %}

Members of I2P will held a talk at CLT and PetCon 2009.1

-Two members of the I2P team will be at two forthcoming Linux day and security convention. -On 14th march of 2009 there will be a short talk about general introduction to I2P at the Chemnitz Linux Tag 2009 hold by echelon.
-Echelon and some other members of the I2P family will attend to the Linux meeting the whole two days (Saturday and Sunday) and will be recognizable as I2P family members. Meet them, ask them your questions, show them your props!
-Show your support!
-
-Just 10 days later the Privacy and Data Security convention in Dresden will take place.
+{% block content %}{% trans -%}

+Members of I2P will held a talk at CLT and PetCon 2009.1 +Two members of the I2P team will be at two forthcoming Linux day and security convention.

+On 14th march of 2009 there will be a short talk about general introduction to I2P at the Chemnitz Linux Tag 2009 hold by echelon. +Echelon and some other members of the I2P family will attend to the Linux meeting the whole two days (Saturday and Sunday) and will be recognizable as I2P family members. Meet them, ask them your questions, show them your props! Show your support!

+Just 10 days later the Privacy and Data Security convention in Dresden will take place. Again, echelon will attend this event and hold a short talk about general introduction to I2P. Another talk about the profiling by the I2P clients will be held. -
+{%- endtrans %}

{% endblock %} diff --git a/i2p2www/pages/site/misc/cvs.html b/i2p2www/pages/site/misc/cvs.html index 52365d9d..05ca9df6 100644 --- a/i2p2www/pages/site/misc/cvs.html +++ b/i2p2www/pages/site/misc/cvs.html @@ -1,11 +1,13 @@ {% extends "global/layout.html" %} {% block title %}CVS{% endblock %} -{% block content %}

The I2P sourcecode was kept in a CVS repository. Nowadays it is kept in an Monotone repository. +{% block content %}

{% trans -%} +The I2P sourcecode was kept in a CVS repository. Nowadays it is kept in an Monotone repository. For those who aren't very familiar with CVS, there is a fantastic book on the subject (developers only need to deal with the first chapter - "An Overview of CVS", as subsequent chapters go into some nasty details very few ever need to -touch).

+touch). +{%- endtrans %}

Unix CVS

cvs -d:pserver:anoncvs@cvs.i2p.net:/cvsroot login
@@ -25,6 +27,8 @@ Password: anoncvs

Commits are sent to the CVS mailinglist

-

Humorous quote from WinCVS: "Did you know... Never experiment with new CVS -commands on your working repository. Create a sample module instead."

+

{% trans -%} +Humorous quote from WinCVS: "Did you know... Never experiment with new CVS +commands on your working repository. Create a sample module instead." +{%- endtrans %}

{% endblock %} diff --git a/i2p2www/pages/site/misc/i2ptunnel-migration.html b/i2p2www/pages/site/misc/i2ptunnel-migration.html index 0c5fa751..b585bc3d 100644 --- a/i2p2www/pages/site/misc/i2ptunnel-migration.html +++ b/i2p2www/pages/site/misc/i2ptunnel-migration.html @@ -1,16 +1,18 @@ {% extends "global/layout.html" %} {% block title %}i2ptunnel migration{% endblock %} -{% block content %}

I2PTunnel migration:

+{% block content %}

{% trans -%}I2PTunnel migration:{%- endtrans %}

-

After upgrading to the new architecture, you'll have to do a +

{% trans -%} +After upgrading to the new architecture, you'll have to do a little work to get your old I2PTunnel-driven servers running. Lets walk through a simple example. For an eepsite with the -old clientApp configuration, you had:

+old clientApp configuration, you had: +{%- endtrans %}

   -e "server localhost 80 myWebPriv.dat"
-

To provide that same functionality on the new web architecture:

+

{% trans -%}To provide that same functionality on the new web architecture:{%- endtrans %}

-

That's it! Creating a new I2PTunnel server works the same way too, except you +

{% trans -%} +That's it! Creating a new I2PTunnel server works the same way too, except you don't need to "copy the old file", obviously. Behind the scenes, it is all driven by the i2ptunnel.config file, which you may modify externally (if you do, hit "Reload config" on the I2PTunnel web page, which will tear down all of your -existing tunnels and rebuild new ones)

+existing tunnels and rebuild new ones) +{%- endtrans %}

-

Note that you WILL need to wait until your router is integrated +

{% trans -%} +Note that you WILL need to wait until your router is integrated into the network before you are able to use the /i2ptunnel/ web interface. It will say "Please be patient" if you try to beforehand, which means that it is still trying to build the -necessary I2PTunnel sessions it has been configured to create.

{% endblock %} +necessary I2PTunnel sessions it has been configured to create. +{%- endtrans %}

{% endblock %} diff --git a/i2p2www/pages/site/misc/i2ptunnel-services.html b/i2p2www/pages/site/misc/i2ptunnel-services.html index a9e9433a..5fec5bc5 100644 --- a/i2p2www/pages/site/misc/i2ptunnel-services.html +++ b/i2p2www/pages/site/misc/i2ptunnel-services.html @@ -1,109 +1,112 @@ {% extends "global/layout.html" %} {% block title %}i2ptunnel services{% endblock %} -{% block content %}Below is quick copy of aum's eepsite deployment guide. -
+{% block content %}{% trans -%} +Below is quick copy of aum's eepsite deployment guide. +{%- endtrans %}

-1. - Deploy a local server -
  • Try to start I2P using $I2P/i2prouter start
    • +
  • {% trans %}Try to start I2P using $I2P/i2prouter start{% endtrans %}
  • tail -f /tmp/wrapper.log and look for any problems.
    • -If this did not work you'll need to use runplain.sh to start I2P. +{% trans %}If this did not work you'll need to use runplain.sh to start I2P.{% endtrans %} {% endblock %} diff --git a/i2p2www/pages/site/misc/minwww.html b/i2p2www/pages/site/misc/minwww.html index a4307741..658df060 100644 --- a/i2p2www/pages/site/misc/minwww.html +++ b/i2p2www/pages/site/misc/minwww.html @@ -1,13 +1,17 @@ {% extends "global/layout.html" %} {% block title %}minwww{% endblock %} -{% block content %}

    Here's an outline and rationale for a minimal WWW proxy app for use over -I2P.

    -

    HTTP operation over I2P using I2PTunnel. When the base SocketLibrary +{% block content %}

    {% trans -%} +Here's an outline and rationale for a minimal WWW proxy app for use over +I2P. +{%- endtrans %}

    +

    {% trans -%} +HTTP operation over I2P using I2PTunnel. When the base SocketLibrary is out, the only significant difference will be the 'wrapRequest' and 'unwrapRequest' will functionally be placed in the socketLibrary, not in the router (but later versions of the SocketLibrary will be able to use selective ACK and large window sizes, allowing more ACKs to be -skipped)

    +skipped) +{%- endtrans %}

     ---BROWSER--->-I2PTUNNEL--->-ROUTERA--->-ROUTERB--->-I2PTUNNEL--->-HTTPD----------
  1: openCon
@@ -38,8 +42,10 @@ skipped)
    
 26:                         receiveACK               receiveClose
 27:            sentSuccess
    -

    An optimized form, designed to handle only 128KB [1] files and pages, can -operate significantly faster:

    +

    {% trans -%} +An optimized form, designed to handle only 128KB [1] files and pages, can +operate significantly faster: +{%- endtrans %}

        BROWSER --> MinWWW   --> ROUTERA --> ROUTERB --> MinWWW    --> HTTPD
  1: openCon
@@ -59,7 +65,8 @@ operate significantly faster:
    
 15: closeCon
 16:            closed
    -

    The difference in network load and latency is significant - this is +

    {% trans -%} +The difference in network load and latency is significant - this is essentially a UDP version of HTTP. On the normal web, we can't really do that, since most HTTP requests and responses are orders of magnitude larger than UDP packets functionally support, but in I2P, messages can be large. The savings @@ -67,20 +74,26 @@ for the network load comes from the fact that we don't need to send any ACK messages - rather than the earlier wrap/unwrap request (that bundles a DataMessage with a DeliveryStatusMessage to provide guaranteed delivery), the MinWWW proxy deals with resends (if necessary - in I2PTunnel today, there are no -resends).

    -

    The data that the MinWWW proxy and server need to wrap is trivial - when the +resends). +{%- endtrans %}

    +

    {% trans -%} +The data that the MinWWW proxy and server need to wrap is trivial - when the proxy wants to send "GET /", it prepends it with the I2P Destination sending the request, followed by a 4 byte request ID. The MinWWW server receives those requests, contacts the appropriate HTTPD, sends the request, waits for the response, and sends a reply to the MinWWW proxy containing the response, prefixed with the original request ID. That response is taken and passed back -to the browser and the connection is closed.

    -

    In addition, the MinWWW proxy can choose the MinWWW server to use from a +to the browser and the connection is closed. +{%- endtrans %}

    +

    {% trans -%} +In addition, the MinWWW proxy can choose the MinWWW server to use from a list, going through some round robin or other algorithm, so that there are multiple outproxies merged transparently. The bandwidth required for running one of these outproxies is also greatly reduced, since it will only handle 128KB -files (aka no one is going to be downloading porn, warez, etc).

    -

    The functionality /is/ limited, but 128KB of data is a lot for a single HTTP +files (aka no one is going to be downloading porn, warez, etc). +{%- endtrans %}

    +

    {% trans -%} +The functionality /is/ limited, but 128KB of data is a lot for a single HTTP request or response. The above diagrams are also unrealistic in their hops - ROUTERA will really never talk directly to ROUTERB. ROUTERA will send each of the messages through two additional outbound routers, then forwarded to @@ -88,16 +101,21 @@ two additional inbound routers to ROUTERB, so the lag there is significant - while the above only saves 11 steps, 8 of those steps need to traverse the entire tunnel path (4+ remote hops each time when tunnels are 2 remote hops in each stretch), leaving MinWWW with only two full traversals (one for the -request, one for the response), instead of 10.

    -

    Implementing the MinWWW proxy and server should be fairly easy - read an HTTP +request, one for the response), instead of 10. +{%- endtrans %}

    +

    {% trans -%} +Implementing the MinWWW proxy and server should be fairly easy - read an HTTP request from the client fully (perhaps only start out with HTTP GET, leaving HTTP POST for later), wrap the message, and wait for the response. The server in turn simply needs to parse the request to either open a socket or URL, send the request, wait for the response, and send it back through the network. -If someone were to implement this, it would be Good :)

    -

    [1] Why 128KB files? Currently I2CP allows functionally arbitrary message +If someone were to implement this, it would be Good :) +{%- endtrans %}

    +

    {% trans -%} +[1] Why 128KB files? Currently I2CP allows functionally arbitrary message size, but that's going to be going away since it involves either excessive memory overhead on intermediary routers, or additional implementation details to handle. I2PTunnel is currently limited to 128KB and hasn't been a burden, -so perhaps it could be increased to 256KB when the I2CP spec is updated)

    +so perhaps it could be increased to 256KB when the I2CP spec is updated) +{%- endtrans %}

    {% endblock %} diff --git a/i2p2www/pages/site/misc/myi2p.html b/i2p2www/pages/site/misc/myi2p.html index e78b1b93..a0b15440 100644 --- a/i2p2www/pages/site/misc/myi2p.html +++ b/i2p2www/pages/site/misc/myi2p.html @@ -1,12 +1,14 @@ {% extends "global/layout.html" %} {% block title %}MYI2P{% endblock %} -{% block content %}

    There has been discussion about a distributed blogging application for a few +{% block content %}

    {% trans -%} +There has been discussion about a distributed blogging application for a few months now called "MyI2P". While the original discussions were lost, we were able to retrieve a Google cache of it. It isn't pretty, but it includes the basic overview and some discussion -that ensued.

    +that ensued.{%- endtrans %}

    -

    The application itself is not yet implemented, and the ideas behind it have +

    {% trans -%} +The application itself is not yet implemented, and the ideas behind it have been made less ambitious over time, but they are still valid and the current plan is to have the core MyI2P functionality available along side the I2P 1.0 release. That will include a distributed address book @@ -19,12 +21,15 @@ system using a reduced and secured subset of bbcode to essentially provide an anonymous LiveJournal with a 'friends list' and transparent access control (authenticated by the I2P -datagrams with rules defined based on the address book).

    +datagrams with rules defined based on the address book). +{%- endtrans %}

    -

    Additional functionality, such as integration with a DHT backing store or +

    {% trans -%} +Additional functionality, such as integration with a DHT backing store or swarming file transfers for 'attachments' can be added later. Email may or may not get in the first pass either, though its implementation is essentially just a blog entry with private access, so perhaps some UI designer can come up with something. Exporting the data to RSS or access through ATOM will be an option -down the road as well.

    +down the road as well. +{%- endtrans %}

    {% endblock %} diff --git a/i2p2www/pages/site/misc/ratestats.html b/i2p2www/pages/site/misc/ratestats.html index 83cd79b7..7ad450c1 100644 --- a/i2p2www/pages/site/misc/ratestats.html +++ b/i2p2www/pages/site/misc/ratestats.html @@ -1,15 +1,15 @@ {% extends "global/layout.html" %} {% block title %}RateStat list{% endblock %} {% block content %} -

    RateStat list

    -

    I2P enables the collection of a wide range of rates, the list published here is accurate as of I2P version 0.8.7.

    -

    The list was gathered using the following command in the top directory of the branch i2p.i2p, +

    {% trans %}RateStat list{% endtrans %}

    +

    {% trans %}I2P enables the collection of a wide range of rates, the list published here is accurate as of I2P version 0.8.7.{% endtrans %}

    +

    {% trans %}The list was gathered using the following command in the top directory of the branch i2p.i2p, 

     find . -name '*' -print | xargs --max-args=3 grep -n --color=auto addRateData | awk 'match($0, /addRateData\(\"(.*)\"/, a) {print a[1]}' | awk '!_[$0]++' | sort > rates.txt
    -All options aren't needed, but it works. +All options aren't needed, but it works.{% endtrans %}

    -

    RateStats

    +

    {% trans %}RateStats{% endtrans %}

     bwLimiter.inboundDelayedTime
 bwLimiter.outboundDelayedTime
diff --git a/i2p2www/pages/site/misc/transition-guide.html b/i2p2www/pages/site/misc/transition-guide.html
index 4480f02d..119eb5ea 100644
--- a/i2p2www/pages/site/misc/transition-guide.html
+++ b/i2p2www/pages/site/misc/transition-guide.html
@@ -1,6 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}Monotone{% endblock %}
-{% block content %}
    The I2P sourcecode is kept in several distributed monotone repositories.
+{% block content %}
    {% trans -%}
+The I2P sourcecode is kept in several distributed monotone repositories.
 See the
 Monotone website for information
 on monotone.
@@ -9,17 +10,17 @@ See
 for more information on how to get started and check out the source anonymously.
 There is also a quick-start guide on the
 new developer's page.
-
    
+{%- endtrans %}
    
 
-
    
+
    {% trans -%}
 If you want to get the source non-anonymously, pull from the public server mtn.welterde.de.
 The i2p source code branch is "i2p.i2p".
-
    
+{%- endtrans %}
    
 
-
    Guide
    
-
    
+
    {% trans %} Guide {% endtrans %}
    
+
    {%- trans %}
 The following is a detailed guide by Complication.
-
    
+{%- endtrans %}
    
 
       {% include "site/misc/transition-guide.txt" %}
 
    
diff --git a/i2p2www/pages/site/misc/upgrade-0.6.1.30.html b/i2p2www/pages/site/misc/upgrade-0.6.1.30.html
index 0d5b3e2c..91dd2d46 100644
--- a/i2p2www/pages/site/misc/upgrade-0.6.1.30.html
+++ b/i2p2www/pages/site/misc/upgrade-0.6.1.30.html
@@ -3,21 +3,24 @@
 {% block content %}
 
    
 •
-2008-02-05: Upgrading from 0.6.1.30 and Earlier Releases
-
    
+2008-02-05: {% trans %}Upgrading from 0.6.1.30 and Earlier Releases{% endtrans %}
+
    
+
    {% trans -%}
 Since i2p's lead developer
 has gone AWOL,
 we do not have his update signing key or access to
 www.i2p[.net] or dev.i2p[.net].
 Complication and zzz have generated new signing keys, and they and Amiga are providing
 update file hosting. These changes must be configured in your router to take effect.
-
    
+{%- endtrans %}
    
+
    {% trans -%}
 Make the following configuration changes and your router will automatically install
 the latest release.
-
    
+{%- endtrans %}
    
+
    {% trans -%}
 We recommend the automated process as it will verify the key of the signed update file.
 If you do not make these changes,
-you may manually download the i2pupdate.zip file from
+you may manually download the i2pupdate.zip file from{% endtrans %}
 the download page.
 
    1. 
 On
@@ -25,7 +28,7 @@ On
 
      1. 
 Change the News URL to: http://complication.i2p/news.xml
 
      2. 
-Select ONE of the following new Update URLs at random and enter it into the Update URL box: 
+{% trans %}Select ONE of the following new Update URLs at random and enter it into the Update URL box: {% endtrans %}
 
        http://amiga.i2p/i2p/i2pupdate.sud
 
        http://complication.i2p/i2p/i2pupdate.sud
 
        http://stats.i2p/i2p/i2pupdate.sud
@@ -44,17 +47,18 @@ Add the following line:
 
      3. 
 Click "Apply"
 
      
-
    2. 
-You are now ready to automatically receive the release update file,
+
    3. {% trans -%}You are now ready to automatically receive the release update file,
 either by setting your update policy to "download and install" or by clicking on the
 "update available" link when it appears.
-
    
-
    
+{%- endtrans %}
+
    
+
    {% trans -%}
 If you would like to verify the trusted update keys, they are also
 posted and signed here.
 Thank you for your support during this transition. For help please contact us on #i2p.
-
    
+{%- endtrans %}
    
+
    {% trans -%}
 Amiga, Complication, welterde, zzz
-
    
+{%- endtrans %}
    
 
 {% endblock %}