From 1099e6bdef06e8d34fc4020bd46d7b7aa774ad4d Mon Sep 17 00:00:00 2001 From: str4d Date: Sun, 5 Jan 2014 04:58:32 +0000 Subject: [PATCH] Added new translations --- i2p2www/translations/pl/LC_MESSAGES/about.po | 2200 +++++++++++++++++ .../translations/pt_BR/LC_MESSAGES/misc.po | 1232 +++++++++ .../translations/zh_CN/LC_MESSAGES/about.po | 2193 ++++++++++++++++ 3 files changed, 5625 insertions(+) create mode 100644 i2p2www/translations/pl/LC_MESSAGES/about.po create mode 100644 i2p2www/translations/pt_BR/LC_MESSAGES/misc.po create mode 100644 i2p2www/translations/zh_CN/LC_MESSAGES/about.po diff --git a/i2p2www/translations/pl/LC_MESSAGES/about.po b/i2p2www/translations/pl/LC_MESSAGES/about.po new file mode 100644 index 00000000..5fd93742 --- /dev/null +++ b/i2p2www/translations/pl/LC_MESSAGES/about.po @@ -0,0 +1,2200 @@ +# Polish translations for I2P. +# Copyright (C) 2013 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# sebx, 2014 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2013-12-30 05:56+0000\n" +"PO-Revision-Date: 2014-01-01 18:01+0000\n" +"Last-Translator: sebx\n" +"Language-Team: Polish " +"(http://www.transifex.com/projects/p/I2P/language/pl/)\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && " +"(n%100<10 || n%100>=20) ? 1 : 2)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 0.9.6\n" + +#: i2p2www/pages/site/about/browser-config.html:2 +msgid "Web Browser Configuration" +msgstr "Konfiguracja Przeglądarki" + +#: i2p2www/pages/site/about/browser-config.html:5 +msgid "" +"Your web browser will need to be configured in order to browse eepsites " +"and to\n" +"utilize the outproxies available within I2P. Below are walkthroughs for " +"some of\n" +"the most popular browsers." +msgstr "" +"Twoja przeglądarka będzie musiała być skonfigurowana po to aby wyświetlać" +" eepsites i \n" +"wykorzystać proxy dostępne w I2P. Poniżej przedstawione są kroki dla \n" +"najbardziej znanych przeglądarek." + +#: i2p2www/pages/site/about/browser-config.html:11 +msgid "How to configure your browser" +msgstr "Jak skonfigurować Twoją przeglądarkę" + +#: i2p2www/pages/site/about/browser-config.html:17 +#: i2p2www/pages/site/about/browser-config.html:73 +msgid "Outproxy Terms Of Service" +msgstr "Outproxy Warunki Korzystania" + +#: i2p2www/pages/site/about/browser-config.html:22 +msgid "Internet Explorer 8 or Chrome" +msgstr "Internet Explorer 8 albo Chrome" + +#: i2p2www/pages/site/about/browser-config.html:23 +msgid "" +"In the tools menu select the \"Internet Options\" line to open the " +"settings. In the\n" +"settings window choose the connections tab and click on LAN settings for " +"the\n" +"proxy port configuration." +msgstr "" +"W pasku narzędzi wybierz \"Opcje Internetowe\" aby otworzyć ustawienia. \n" +"Wybierz tab połączeń i kliknij na ustawienia LAN dla \n" +"konfiguracji proxy." + +#: i2p2www/pages/site/about/browser-config.html:28 +msgid "IE Internet Options" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:29 +msgid "" +"Now set the checkmark at \"use a proxy server for your LAN\" and at the " +"\"Bypass\n" +"proxy server for local addresses\". With a click on Advanced-button you " +"open the\n" +"window to open the ports. Enter the values like on the picture, IP " +"127.0.0.1\n" +"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save " +"the\n" +"settings and your browser is set to use the I2P proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:36 +msgid "IE Proxy Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:40 +msgid "" +"From the Tools menu, select Options to bring up the Firefox settings " +"panel.\n" +"Click the icon labelled Advanced, then click on the " +"Network\n" +"tab. In the Connections section, click on the Settings button. " +"You'll\n" +"see a Window like the following:" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:46 +msgid "Firefox Network Options" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:47 +msgid "" +"In the Connection Settings window, click the circle next to " +"Manual\n" +" proxy configuration, then enter 127.0.0.1, port 4444 in the HTTP" +" Proxy\n" +"field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.\n" +"Be sure to enter localhost and 127.0.0.1 into the \"No Proxy for\" box." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:53 +msgid "Firefox Proxy Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:57 +msgid "" +"From the Settings menu, select Configure Konqueror. In " +"the\n" +"Web Browsing group on the left side, select Proxy Services.\n" +"In this new window, select the option \"Manually specify the proxy " +"settings\" and\n" +"click the Setup box." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:63 +msgid "Konqueror Proxy Options" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:64 +msgid "" +"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port" +" 4445 into\n" +"HTTPS box. Click the New button in the Exceptions section. Enter" +"\n" +"localhost and click OK. Click the New button once more and enter" +"\n" +"127.0.0.1 and OK. Hit OK once more to close the configuration window." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:70 +msgid "Konqueror Proxy Ports" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:74 +msgid "" +"Remember: I2P was not designed for creating proxies to the outer " +"Internet.\n" +"Instead, it is meant to be used as an internal network." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:78 +msgid "" +"The I2P project itself does not run any proxies to the Internet. Any " +"such proxy\n" +"services are run by by private volunteers and could be shut down or\n" +"unreachable at anytime." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:83 +#, python-format +msgid "" +"By default, I2P comes with two outproxies configured: " +"%(http)s\n" +"(an HTTP-only proxy) and %(https)s (an HTTPS proxy\n" +"routed through Tor." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:88 +msgid "" +"Both of these outproxies are configured with connection limits. This " +"means\n" +"that only set amount of accesses are allowed per client. Once the limit " +"is\n" +"reached, the client is blocked out for a timeframe of 1min/1h/1 day. Be\n" +"respectful and do not overload these services with too many requests!" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:94 +msgid "" +"Filtering is active on these outproxies (for example, mibbit and torrent\n" +"tracker access is blocked). Eepsites\n" +"that are accessible via .i2p addresses are also not allowed via the " +"outproxies.\n" +"As a convenience, false.i2p blocks ad servers." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:100 +msgid "" +"Tor is good application to use" +" as an\n" +"outproxy to the Internet." +msgstr "" + +#: i2p2www/pages/site/about/glossary.html:2 +msgid "Glossary" +msgstr "" + +#: i2p2www/pages/site/about/glossary.html:4 +msgid "" +"This page lists often-used terminology when discussing I2P and " +"cryptography." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:2 +msgid "Hall Of Fame" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:5 +msgid "I2P's Hall of Fame" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:6 +#, python-format +msgid "Current balance: as of %(date)s" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:9 +#: i2p2www/pages/site/about/hall-of-fame.html:47 +#: i2p2www/pages/site/about/hall-of-fame.html:173 +#: i2p2www/pages/site/about/hall-of-fame.html:174 +#: i2p2www/pages/site/about/hall-of-fame.html:175 +#: i2p2www/pages/site/about/hall-of-fame.html:176 +#: i2p2www/pages/site/about/hall-of-fame.html:178 +#: i2p2www/pages/site/about/hall-of-fame.html:179 +#: i2p2www/pages/site/about/hall-of-fame.html:180 +#: i2p2www/pages/site/about/hall-of-fame.html:183 +#: i2p2www/pages/site/about/hall-of-fame.html:184 +#: i2p2www/pages/site/about/hall-of-fame.html:185 +#: i2p2www/pages/site/about/hall-of-fame.html:188 +#: i2p2www/pages/site/about/hall-of-fame.html:189 +#: i2p2www/pages/site/about/hall-of-fame.html:190 +#: i2p2www/pages/site/about/hall-of-fame.html:191 +#: i2p2www/pages/site/about/hall-of-fame.html:192 +#: i2p2www/pages/site/about/hall-of-fame.html:193 +#: i2p2www/pages/site/about/hall-of-fame.html:194 +#: i2p2www/pages/site/about/hall-of-fame.html:195 +#: i2p2www/pages/site/about/hall-of-fame.html:196 +#: i2p2www/pages/site/about/hall-of-fame.html:197 +#: i2p2www/pages/site/about/hall-of-fame.html:198 +#: i2p2www/pages/site/about/hall-of-fame.html:199 +#: i2p2www/pages/site/about/hall-of-fame.html:200 +#: i2p2www/pages/site/about/hall-of-fame.html:203 +#: i2p2www/pages/site/about/hall-of-fame.html:204 +#: i2p2www/pages/site/about/hall-of-fame.html:205 +#: i2p2www/pages/site/about/hall-of-fame.html:206 +#: i2p2www/pages/site/about/hall-of-fame.html:207 +#: i2p2www/pages/site/about/hall-of-fame.html:208 +#: i2p2www/pages/site/about/hall-of-fame.html:210 +#: i2p2www/pages/site/about/hall-of-fame.html:211 +#: i2p2www/pages/site/about/hall-of-fame.html:214 +#: i2p2www/pages/site/about/hall-of-fame.html:215 +#: i2p2www/pages/site/about/hall-of-fame.html:216 +#: i2p2www/pages/site/about/hall-of-fame.html:217 +#: i2p2www/pages/site/about/hall-of-fame.html:218 +#: i2p2www/pages/site/about/hall-of-fame.html:220 +#: i2p2www/pages/site/about/hall-of-fame.html:221 +#: i2p2www/pages/site/about/hall-of-fame.html:222 +#: i2p2www/pages/site/about/hall-of-fame.html:223 +#: i2p2www/pages/site/about/hall-of-fame.html:224 +#: i2p2www/pages/site/about/hall-of-fame.html:225 +#: i2p2www/pages/site/about/hall-of-fame.html:227 +#: i2p2www/pages/site/about/hall-of-fame.html:228 +#: i2p2www/pages/site/about/hall-of-fame.html:229 +#: i2p2www/pages/site/about/hall-of-fame.html:230 +#: i2p2www/pages/site/about/hall-of-fame.html:232 +#: i2p2www/pages/site/about/hall-of-fame.html:233 +#: i2p2www/pages/site/about/hall-of-fame.html:234 +#: i2p2www/pages/site/about/hall-of-fame.html:235 +#: i2p2www/pages/site/about/hall-of-fame.html:236 +#: i2p2www/pages/site/about/hall-of-fame.html:239 +#: i2p2www/pages/site/about/hall-of-fame.html:240 +#: i2p2www/pages/site/about/hall-of-fame.html:241 +#: i2p2www/pages/site/about/hall-of-fame.html:242 +#: i2p2www/pages/site/about/hall-of-fame.html:244 +#: i2p2www/pages/site/about/hall-of-fame.html:245 +#: i2p2www/pages/site/about/hall-of-fame.html:246 +#: i2p2www/pages/site/about/hall-of-fame.html:248 +#: i2p2www/pages/site/about/hall-of-fame.html:249 +#: i2p2www/pages/site/about/hall-of-fame.html:250 +#: i2p2www/pages/site/about/hall-of-fame.html:251 +#: i2p2www/pages/site/about/hall-of-fame.html:253 +#: i2p2www/pages/site/about/hall-of-fame.html:254 +#: i2p2www/pages/site/about/hall-of-fame.html:255 +#: i2p2www/pages/site/about/hall-of-fame.html:256 +#: i2p2www/pages/site/about/hall-of-fame.html:257 +#: i2p2www/pages/site/about/hall-of-fame.html:263 +#: i2p2www/pages/site/about/hall-of-fame.html:266 +#: i2p2www/pages/site/about/hall-of-fame.html:267 +#: i2p2www/pages/site/about/hall-of-fame.html:268 +#: i2p2www/pages/site/about/hall-of-fame.html:269 +#: i2p2www/pages/site/about/hall-of-fame.html:270 +#: i2p2www/pages/site/about/hall-of-fame.html:272 +#: i2p2www/pages/site/about/hall-of-fame.html:273 +#: i2p2www/pages/site/about/hall-of-fame.html:274 +#: i2p2www/pages/site/about/hall-of-fame.html:279 +#: i2p2www/pages/site/about/hall-of-fame.html:280 +#: i2p2www/pages/site/about/hall-of-fame.html:281 +#: i2p2www/pages/site/about/hall-of-fame.html:282 +#: i2p2www/pages/site/about/hall-of-fame.html:283 +#: i2p2www/pages/site/about/hall-of-fame.html:284 +#: i2p2www/pages/site/about/hall-of-fame.html:285 +#: i2p2www/pages/site/about/hall-of-fame.html:286 +#: i2p2www/pages/site/about/hall-of-fame.html:287 +#: i2p2www/pages/site/about/hall-of-fame.html:288 +#: i2p2www/pages/site/about/hall-of-fame.html:290 +#: i2p2www/pages/site/about/hall-of-fame.html:291 +#: i2p2www/pages/site/about/hall-of-fame.html:301 +#: i2p2www/pages/site/about/hall-of-fame.html:302 +#: i2p2www/pages/site/about/hall-of-fame.html:303 +#: i2p2www/pages/site/about/hall-of-fame.html:304 +#: i2p2www/pages/site/about/hall-of-fame.html:305 +#: i2p2www/pages/site/about/hall-of-fame.html:306 +#: i2p2www/pages/site/about/hall-of-fame.html:307 +#: i2p2www/pages/site/about/hall-of-fame.html:308 +#: i2p2www/pages/site/about/hall-of-fame.html:309 +#: i2p2www/pages/site/about/hall-of-fame.html:310 +#: i2p2www/pages/site/about/hall-of-fame.html:311 +#: i2p2www/pages/site/about/hall-of-fame.html:312 +#: i2p2www/pages/site/about/hall-of-fame.html:313 +#: i2p2www/pages/site/about/hall-of-fame.html:314 +#: i2p2www/pages/site/about/hall-of-fame.html:315 +#: i2p2www/pages/site/about/hall-of-fame.html:316 +#: i2p2www/pages/site/about/hall-of-fame.html:317 +#: i2p2www/pages/site/about/hall-of-fame.html:318 +#: i2p2www/pages/site/about/hall-of-fame.html:319 +#: i2p2www/pages/site/about/hall-of-fame.html:320 +#: i2p2www/pages/site/about/hall-of-fame.html:321 +#: i2p2www/pages/site/about/hall-of-fame.html:325 +#: i2p2www/pages/site/about/hall-of-fame.html:326 +#: i2p2www/pages/site/about/hall-of-fame.html:327 +#: i2p2www/pages/site/about/hall-of-fame.html:328 +#: i2p2www/pages/site/about/hall-of-fame.html:329 +#: i2p2www/pages/site/about/hall-of-fame.html:330 +#: i2p2www/pages/site/about/hall-of-fame.html:331 +#: i2p2www/pages/site/about/hall-of-fame.html:333 +#: i2p2www/pages/site/about/hall-of-fame.html:334 +#: i2p2www/pages/site/about/hall-of-fame.html:335 +#: i2p2www/pages/site/about/hall-of-fame.html:336 +#: i2p2www/pages/site/about/hall-of-fame.html:337 +#: i2p2www/pages/site/about/hall-of-fame.html:338 +#: i2p2www/pages/site/about/hall-of-fame.html:339 +#: i2p2www/pages/site/about/hall-of-fame.html:340 +#: i2p2www/pages/site/about/hall-of-fame.html:341 +#: i2p2www/pages/site/about/hall-of-fame.html:344 +#: i2p2www/pages/site/about/hall-of-fame.html:345 +#: i2p2www/pages/site/about/hall-of-fame.html:346 +#: i2p2www/pages/site/about/hall-of-fame.html:347 +#: i2p2www/pages/site/about/hall-of-fame.html:348 +#: i2p2www/pages/site/about/hall-of-fame.html:350 +#: i2p2www/pages/site/about/hall-of-fame.html:352 +#: i2p2www/pages/site/about/hall-of-fame.html:353 +#: i2p2www/pages/site/about/hall-of-fame.html:354 +#: i2p2www/pages/site/about/hall-of-fame.html:355 +#: i2p2www/pages/site/about/hall-of-fame.html:356 +#: i2p2www/pages/site/about/hall-of-fame.html:357 +#: i2p2www/pages/site/about/hall-of-fame.html:358 +#: i2p2www/pages/site/about/hall-of-fame.html:360 +#: i2p2www/pages/site/about/hall-of-fame.html:361 +#: i2p2www/pages/site/about/hall-of-fame.html:362 +#: i2p2www/pages/site/about/hall-of-fame.html:363 +#: i2p2www/pages/site/about/hall-of-fame.html:364 +#: i2p2www/pages/site/about/hall-of-fame.html:365 +#: i2p2www/pages/site/about/hall-of-fame.html:366 +#: i2p2www/pages/site/about/hall-of-fame.html:367 +#: i2p2www/pages/site/about/hall-of-fame.html:368 +#: i2p2www/pages/site/about/hall-of-fame.html:369 +#: i2p2www/pages/site/about/hall-of-fame.html:370 +#: i2p2www/pages/site/about/hall-of-fame.html:371 +#: i2p2www/pages/site/about/hall-of-fame.html:372 +#: i2p2www/pages/site/about/hall-of-fame.html:373 +#: i2p2www/pages/site/about/hall-of-fame.html:375 +#: i2p2www/pages/site/about/hall-of-fame.html:376 +#: i2p2www/pages/site/about/hall-of-fame.html:377 +#: i2p2www/pages/site/about/hall-of-fame.html:380 +#: i2p2www/pages/site/about/hall-of-fame.html:381 +#: i2p2www/pages/site/about/hall-of-fame.html:384 +#: i2p2www/pages/site/about/hall-of-fame.html:385 +#: i2p2www/pages/site/about/hall-of-fame.html:387 +#: i2p2www/pages/site/about/hall-of-fame.html:388 +#: i2p2www/pages/site/about/hall-of-fame.html:401 +#: i2p2www/pages/site/about/hall-of-fame.html:402 +#: i2p2www/pages/site/about/hall-of-fame.html:403 +#: i2p2www/pages/site/about/hall-of-fame.html:404 +#: i2p2www/pages/site/about/hall-of-fame.html:405 +#: i2p2www/pages/site/about/hall-of-fame.html:406 +#: i2p2www/pages/site/about/hall-of-fame.html:407 +#: i2p2www/pages/site/about/hall-of-fame.html:408 +#: i2p2www/pages/site/about/hall-of-fame.html:409 +#: i2p2www/pages/site/about/hall-of-fame.html:410 +#: i2p2www/pages/site/about/hall-of-fame.html:411 +#: i2p2www/pages/site/about/hall-of-fame.html:412 +#: i2p2www/pages/site/about/hall-of-fame.html:413 +#: i2p2www/pages/site/about/hall-of-fame.html:414 +#: i2p2www/pages/site/about/hall-of-fame.html:415 +#: i2p2www/pages/site/about/hall-of-fame.html:416 +#: i2p2www/pages/site/about/hall-of-fame.html:417 +#: i2p2www/pages/site/about/hall-of-fame.html:418 +#: i2p2www/pages/site/about/hall-of-fame.html:419 +#: i2p2www/pages/site/about/hall-of-fame.html:420 +#: i2p2www/pages/site/about/hall-of-fame.html:421 +#: i2p2www/pages/site/about/hall-of-fame.html:422 +#: i2p2www/pages/site/about/hall-of-fame.html:423 +#: i2p2www/pages/site/about/hall-of-fame.html:424 +#: i2p2www/pages/site/about/hall-of-fame.html:425 +#: i2p2www/pages/site/about/hall-of-fame.html:426 +#: i2p2www/pages/site/about/hall-of-fame.html:427 +#: i2p2www/pages/site/about/hall-of-fame.html:428 +#: i2p2www/pages/site/about/hall-of-fame.html:429 +#: i2p2www/pages/site/about/hall-of-fame.html:430 +#: i2p2www/pages/site/about/hall-of-fame.html:431 +#: i2p2www/pages/site/about/hall-of-fame.html:432 +#: i2p2www/pages/site/about/hall-of-fame.html:433 +#: i2p2www/pages/site/about/hall-of-fame.html:434 +#: i2p2www/pages/site/about/hall-of-fame.html:435 +#: i2p2www/pages/site/about/hall-of-fame.html:437 +#: i2p2www/pages/site/about/hall-of-fame.html:438 +#: i2p2www/pages/site/about/hall-of-fame.html:439 +#: i2p2www/pages/site/about/hall-of-fame.html:440 +#: i2p2www/pages/site/about/hall-of-fame.html:441 +#: i2p2www/pages/site/about/hall-of-fame.html:442 +#: i2p2www/pages/site/about/hall-of-fame.html:443 +#: i2p2www/pages/site/about/hall-of-fame.html:444 +#: i2p2www/pages/site/about/hall-of-fame.html:446 +#: i2p2www/pages/site/about/hall-of-fame.html:447 +#: i2p2www/pages/site/about/hall-of-fame.html:448 +#: i2p2www/pages/site/about/hall-of-fame.html:450 +#: i2p2www/pages/site/about/hall-of-fame.html:451 +#: i2p2www/pages/site/about/hall-of-fame.html:452 +#: i2p2www/pages/site/about/hall-of-fame.html:453 +#: i2p2www/pages/site/about/hall-of-fame.html:454 +#: i2p2www/pages/site/about/hall-of-fame.html:456 +#: i2p2www/pages/site/about/hall-of-fame.html:459 +#: i2p2www/pages/site/about/hall-of-fame.html:460 +#: i2p2www/pages/site/about/hall-of-fame.html:461 +#: i2p2www/pages/site/about/hall-of-fame.html:462 +#: i2p2www/pages/site/about/hall-of-fame.html:463 +#: i2p2www/pages/site/about/hall-of-fame.html:464 +#: i2p2www/pages/site/about/hall-of-fame.html:465 +#: i2p2www/pages/site/about/hall-of-fame.html:466 +#: i2p2www/pages/site/about/hall-of-fame.html:467 +#: i2p2www/pages/site/about/hall-of-fame.html:468 +#: i2p2www/pages/site/about/hall-of-fame.html:469 +#: i2p2www/pages/site/about/hall-of-fame.html:470 +#: i2p2www/pages/site/about/hall-of-fame.html:471 +#: i2p2www/pages/site/about/hall-of-fame.html:472 +#: i2p2www/pages/site/about/hall-of-fame.html:474 +#: i2p2www/pages/site/about/hall-of-fame.html:475 +#: i2p2www/pages/site/about/hall-of-fame.html:476 +#: i2p2www/pages/site/about/hall-of-fame.html:478 +#: i2p2www/pages/site/about/hall-of-fame.html:481 +#: i2p2www/pages/site/about/hall-of-fame.html:482 +#: i2p2www/pages/site/about/hall-of-fame.html:483 +#: i2p2www/pages/site/about/hall-of-fame.html:484 +#: i2p2www/pages/site/about/hall-of-fame.html:485 +#: i2p2www/pages/site/about/hall-of-fame.html:486 +#: i2p2www/pages/site/about/hall-of-fame.html:487 +#: i2p2www/pages/site/about/hall-of-fame.html:488 +#: i2p2www/pages/site/about/hall-of-fame.html:489 +#: i2p2www/pages/site/about/hall-of-fame.html:490 +#: i2p2www/pages/site/about/hall-of-fame.html:491 +#: i2p2www/pages/site/about/hall-of-fame.html:492 +#: i2p2www/pages/site/about/hall-of-fame.html:493 +#: i2p2www/pages/site/about/hall-of-fame.html:494 +#: i2p2www/pages/site/about/hall-of-fame.html:495 +#: i2p2www/pages/site/about/hall-of-fame.html:496 +#: i2p2www/pages/site/about/hall-of-fame.html:497 +#: i2p2www/pages/site/about/hall-of-fame.html:498 +#: i2p2www/pages/site/about/hall-of-fame.html:499 +#: i2p2www/pages/site/about/hall-of-fame.html:501 +#: i2p2www/pages/site/about/hall-of-fame.html:502 +#: i2p2www/pages/site/about/hall-of-fame.html:503 +msgid "General fund" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:10 +#: i2p2www/pages/site/about/hall-of-fame.html:12 +#: i2p2www/pages/site/about/hall-of-fame.html:14 +#: i2p2www/pages/site/about/hall-of-fame.html:20 +#, python-format +msgid "%(euroval)s € and %(btcval)s BTC" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:11 +msgid "Datastorage bounty" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:13 +msgid "Native IPv6 I2P" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:15 +msgid "I2PHex bounty" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:16 +#: i2p2www/pages/site/about/hall-of-fame.html:18 +#: i2p2www/pages/site/about/hall-of-fame.html:22 +#, python-format +msgid "%(euroval)s €" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:17 +msgid "I2P in debian mirrors" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:19 +msgid "Bitcoin client for I2P" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:21 +msgid "Unit Tests for I2P router" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:23 +msgid "Bounty Robert" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:24 +msgid "Bounty Syndie" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:25 +msgid "Bounty I2P for CCR Microtic Board" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:28 +msgid "Current monthly running costs:" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:39 +msgid "Big thanks go to the following people who have donated to I2P!" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:40 +#, python-format +msgid "" +"If you have made a donation, please send an email to echelon\n" +"with your name or nick (and optionally homepage) so we can list you here." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:45 +msgid "Current monthly subscriptions:" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:51 +msgid "2013 donations and costs:" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:170 +msgid "2012 donations and costs:" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:298 +msgid "2011 donations and costs:" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:399 +msgid "Previous to 2011 donations:" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:2 +msgid "Intro" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:4 +msgid "The Invisible Internet Project" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:5 +#, python-format +msgid "" +"I2P is an anonymous network, exposing a simple layer that applications " +"can \n" +"use to anonymously and securely send messages to each other. The network " +"itself is \n" +"strictly message based (a la IP), but there is a \n" +"library available to allow reliable streaming communication on top of it " +"(a la \n" +"TCP). \n" +"All communication is end to end encrypted (in total there are four layers" +" of \n" +"encryption used when sending a message), and even the end points " +"(\"destinations\") \n" +"are cryptographic identifiers (essentially a pair of public keys)." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:18 +msgid "How does it work?" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:20 +#, python-format +msgid "" +"To anonymize the messages sent, each client application has their I2P " +"\"router\"\n" +"build a few inbound and outbound \"tunnels\" - a \n" +"sequence of peers that pass messages in one direction (to and from the " +"client, \n" +"respectively). In turn, when a client wants to send a message to another" +" client, \n" +"the client passes that message out one of their outbound tunnels " +"targeting one of the \n" +"other client's inbound tunnels, eventually reaching the destination. " +"Every \n" +"participant in the network chooses the length of these tunnels, and in " +"doing so, \n" +"makes a tradeoff between anonymity, latency, and throughput according to " +"their \n" +"own needs. The result is that the number of peers relaying each end to " +"end \n" +"message is the absolute minimum necessary to meet both the sender's and " +"the \n" +"receiver's threat model." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:34 +#, python-format +msgid "" +"The first time a client wants to contact another client, they make a " +"query \n" +"against the fully distributed \"network \n" +"database\" - a custom structured \n" +"distributed hash table (DHT) based off the \n" +"Kademlia algorithm. This is done \n" +"to find the other client's inbound tunnels efficiently, but subsequent " +"messages \n" +"between them usually includes that data so no further network database " +"lookups \n" +"are required." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:47 +#, python-format +msgid "More details about how I2P works are available." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:51 +msgid "What can you do with it?" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:53 +#, python-format +msgid "" +"Within the I2P network, applications are not restricted in how they can \n" +"communicate - those that typically use UDP can make use of the base I2P \n" +"functionality, and those that typically use TCP can use the TCP-like " +"streaming\n" +"library. We have a generic TCP/I2P bridge application \n" +"(\"I2PTunnel\") that enables people to " +"forward TCP streams\n" +"into the I2P network as well as to receive streams out of the network and" +" \n" +"forward them towards a specific TCP/IP address." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:63 +#, python-format +msgid "" +"I2PTunnel is currently used to let people run their own anonymous website" +" \n" +"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel " +"'server' \n" +"at it, which people can access anonymously over I2P with a normal web " +"browser \n" +"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use " +"the same \n" +"technique to run an anonymous IRC network (where the IRC server is hosted" +" \n" +"anonymously, and standard IRC clients use an I2PTunnel to contact it). " +"There \n" +"are other application development efforts going on as well, such as one " +"to \n" +"build an optimized swarming file transfer application (a la \n" +"BitTorrent), a \n" +"distributed data store (a la Freenet / \n" +"MNet), and a blogging system (a fully \n" +"distributed LiveJournal), but those are \n" +"not ready for use yet." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:82 +#, python-format +msgid "" +"I2P is not inherently an \"outproxy\" network - the client you send a " +"message \n" +"to is the cryptographic identifier, not some IP address, so the message " +"must \n" +"be addressed to someone running I2P. However, it is possible for that " +"client\n" +"to be an outproxy, allowing you to anonymously make use of their Internet" +" \n" +"connection. To demonstrate this, the \"eepproxy\" will accept normal " +"non-I2P \n" +"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific " +"destination\n" +"that runs a squid HTTP proxy, allowing \n" +"simple anonymous browsing of the normal web. Simple outproxies like that" +" are \n" +"not viable in the long run for several reasons (including the cost of " +"running \n" +"one as well as the anonymity and security issues they introduce), but in" +" \n" +"certain circumstances the technique could be appropriate." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:96 +#, python-format +msgid "" +"The I2P development team is an open group, " +"welcome to all \n" +"who are interested in getting involved, and" +" all of \n" +"the code is open source. The core I2P SDK " +"and the \n" +"current router implementation is done in Java (currently working with " +"both \n" +"sun and kaffe, gcj support planned for later), and there is a \n" +"simple socket based API for accessing the network" +" from \n" +"other languages (with a C library available, and both Python and Perl in" +" \n" +"development). The network is actively being developed and has not yet " +"reached \n" +"the 1.0 release, but the current roadmap " +"describes \n" +"our schedule." +msgstr "" + +#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4 +msgid "Presentations on I2P" +msgstr "" + +#: i2p2www/pages/site/about/media.html:5 +#, python-format +msgid "" +"Following are links to presentations, videos, and tutorials about I2P. " +"Links to research papers on I2P are available here." +msgstr "" + +#: i2p2www/pages/site/about/media.html:8 +#, python-format +msgid "To request an addition to this page, please send to %(email)s." +msgstr "" + +#: i2p2www/pages/site/about/media.html:11 +msgid "" +"\n" +"Newest links are at the bottom of each section." +msgstr "" + +#: i2p2www/pages/site/about/media.html:16 +msgid "Presentations" +msgstr "" + +#: i2p2www/pages/site/about/media.html:19 +#, python-format +msgid "" +"IIP Presentation at CodeCon\n" +"MP3 audio\n" +"transcript\n" +"Lance James (0x90), February 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:27 +#, python-format +msgid "" +"IIP Presentation at ToorCon\n" +"MP3 audio\n" +"slides\n" +"Lance James (0x90), September 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:35 +#, python-format +msgid "" +"To Be or I2P\n" +"(Youtube Video)\n" +"An introduction into anonymous communication with I2P.\n" +"To Be or I2P (PDF presentation),\n" +"Jens Kubieziel, 24C3 Berlin, December 28, 2007." +msgstr "" + +#: i2p2www/pages/site/about/media.html:44 +#, python-format +msgid "" +"Video of I2P talk at Chemnitz Linux Tag,\n" +"Lars Schimmer,\n" +"March 14-15, 2009" +msgstr "" + +#: i2p2www/pages/site/about/media.html:50 +#, python-format +msgid "" +"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of" +" Adrian Hong's talk\n" +"\"Hackers for Human Rights\".\n" +"MP3 audio" +msgstr "" + +#: i2p2www/pages/site/about/media.html:56 +#, python-format +msgid "" +"Into the I2P Darknet: Welcome to Cipherspace\n" +"Adrian Crenshaw. Schmoocon Firetalk, January 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:61 +#, python-format +msgid "" +"Using techhnology to advance liberty\n" +"(Youtube Video)\n" +"Eric Johnson.\n" +"Agora I/O Unconference, March 27," +" 2011.\n" +"I2P covered from 10:00 to 20:00 in the video." +msgstr "" + +#: i2p2www/pages/site/about/media.html:69 +#, python-format +msgid "" +"The Bright side of darknets, FOSSCOMM Patras May " +"2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:73 +#, python-format +msgid "" +"Common Darknet Weaknesses\n" +"(Youtube Video)\n" +"Adrian Crenshaw, AIDE, July " +"11-15, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:79 +#, python-format +msgid "" +"I2P / Tor Workshop Notes\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:84 +#, python-format +msgid "" +"Cipherspaces/Darknets: An Overview Of Attack " +"Strategies -\n" +"DEF CON Live version (Youtube Video),\n" +"\"Studio\" version (Youtube Video),\n" +"Slides (ppt)\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:94 +msgid "" +"Modern cipherspace ecosystems, 0x375 " +"0x06 4/11/2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:100 +msgid "Tutorials" +msgstr "" + +#: i2p2www/pages/site/about/media.html:103 +#, python-format +msgid "" +"I2P Windows Tutorial\n" +"(Youtube Video)\n" +"This guide will show you how to install I2P in Windows XP.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:111 +#, python-format +msgid "" +"I2P Debian Tutorial\n" +"(Youtube Video)\n" +"This will guide you through how to install I2P on a Debian Linux System.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:119 +#, python-format +msgid "" +"How to set up anonymous site in I2P\n" +"(Youtube Video)\n" +"How to set up an anonymous web site in I2P.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:126 +#, python-format +msgid "" +"I2P Tutorial Mac OS X\n" +"(Youtube Video)\n" +"A tutorial on how to run i2p on Mac OS X and how to connect to " +"irc.telecomix.i2p.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:133 +#, python-format +msgid "" +"Felix Atari explains the basic principles of I2P" +"\n" +"(Youtube Video)\n" +"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:140 +#, python-format +msgid "" +"How to get onto I2P, the anonymous P2P Darknet " +"(Windows Install)\n" +"(Youtube Video)\n" +"This tutorial shows how to install and configure software needed to " +"access I2P." +msgstr "" + +#: i2p2www/pages/site/about/media.html:146 +#, python-format +msgid "" +"How to connect to I2P\n" +"(Youtube Video)\n" +"How to install I2P on Ubuntu." +msgstr "" + +#: i2p2www/pages/site/about/media.html:152 +#, python-format +msgid "" +"Installing the I2P darknet software in Linux\n" +"(Video)\n" +"Adrian Crenshaw.\n" +"January 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:159 +#, python-format +msgid "" +"Short garlic routing animation\n" +"(Youtube Video)\n" +"Adrian Crenshaw.\n" +msgstr "" + +#: i2p2www/pages/site/about/media.html:167 +msgid "Articles and Interviews" +msgstr "" + +#: i2p2www/pages/site/about/media.html:170 +#, python-format +msgid "" +"0x90 Interviewed by DistributedCity\n" +"Part 1\n" +"Part 2\n" +"July 26, 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:178 +#, python-format +msgid "" +"0x90 Interviewed by El Pais\n" +"(original in Spanish)\n" +"English translation\n" +"October 31, 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:185 +#, python-format +msgid "" +"2003 Business Week article referencing " +"invisiblenet" +msgstr "" + +#: i2p2www/pages/site/about/media.html:189 +#, python-format +msgid "" +"Netzwelt.de article about being anonymous in the " +"Internet\n" +"(German)\n" +"November 2007." +msgstr "" + +#: i2p2www/pages/site/about/media.html:195 +#, python-format +msgid "" +"zzz interviewed by gulli.com\n" +"March 2009\n" +"German translation" +msgstr "" + +#: i2p2www/pages/site/about/media.html:202 +#, python-format +msgid "" +"zzz interviewed on the InfoSec Daily Podcast Ep. 454 " +"(mp3)\n" +"August 18, 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:207 +#, python-format +msgid "" +"I2P - Anonymity for the Masses,\n" +"Jonathan Cox,\n" +"November 11, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:213 +#, python-format +msgid "" +"zzz and Lance James interviewed on the InfoSec Daily " +"Podcast Ep. 596 (mp3)\n" +"February 16, 2012" +msgstr "" + +#: i2p2www/pages/site/about/team.html:2 +msgid "Team" +msgstr "" + +#: i2p2www/pages/site/about/team.html:4 +msgid "I2P Project Members" +msgstr "" + +#: i2p2www/pages/site/about/team.html:5 +#, python-format +msgid "" +"We are a small group of people spread around several continents, working " +"to\n" +"advance different aspects of the project and discussing the design of the" +"\n" +"network.\n" +"Get involved!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:14 +msgid "Admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:15 +msgid "Project Manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:17 +msgid "point of contact of last resort" +msgstr "" + +#: i2p2www/pages/site/about/team.html:20 +msgid "Treasurer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:22 +msgid "manage donations / accounts / bounties" +msgstr "" + +#: i2p2www/pages/site/about/team.html:25 +msgid "PR manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:27 +msgid "press contact, manages public relations and affairs" +msgstr "" + +#: i2p2www/pages/site/about/team.html:30 +#, python-format +msgid "Forum admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:32 +msgid "manage the public user forum" +msgstr "" + +#: i2p2www/pages/site/about/team.html:35 +msgid "Mirrors admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:37 +msgid "manage the project mirrors" +msgstr "" + +#: i2p2www/pages/site/about/team.html:40 +#, python-format +msgid "Monotone guru" +msgstr "" + +#: i2p2www/pages/site/about/team.html:42 +msgid "manage the public monotone repositories" +msgstr "" + +#: i2p2www/pages/site/about/team.html:45 +msgid "Packager; Linux" +msgstr "" + +#: i2p2www/pages/site/about/team.html:47 +msgid "Linux (Debian/Ubuntu) distribution packager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:50 +msgid "Packager; Windows" +msgstr "" + +#: i2p2www/pages/site/about/team.html:52 +msgid "Windows installer packager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:55 +msgid "Release Manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:57 +msgid "Builds and signs the releases" +msgstr "" + +#: i2p2www/pages/site/about/team.html:60 +msgid "Update admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:62 +msgid "Monitors and recruits in-network update hosts" +msgstr "" + +#: i2p2www/pages/site/about/team.html:65 +msgid "Reseed admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:67 +msgid "Monitors, advises and recruits reseed hosts" +msgstr "" + +#: i2p2www/pages/site/about/team.html:70 +msgid "Security expert" +msgstr "" + +#: i2p2www/pages/site/about/team.html:71 i2p2www/pages/site/about/team.html:86 +#: i2p2www/pages/site/about/team.html:91 i2p2www/pages/site/about/team.html:111 +#: i2p2www/pages/site/about/team.html:148 +#: i2p2www/pages/site/about/team.html:158 +#: i2p2www/pages/site/about/team.html:163 +#: i2p2www/pages/site/about/team.html:168 +#: i2p2www/pages/site/about/team.html:173 +#: i2p2www/pages/site/about/team.html:178 +#: i2p2www/pages/site/about/team.html:211 +msgid "vacant" +msgstr "" + +#: i2p2www/pages/site/about/team.html:72 +msgid "threat model / crypto expert" +msgstr "" + +#: i2p2www/pages/site/about/team.html:77 +msgid "Manage the project bug tracker" +msgstr "" + +#: i2p2www/pages/site/about/team.html:80 +msgid "Translation admins" +msgstr "" + +#: i2p2www/pages/site/about/team.html:85 +msgid "User Advocate" +msgstr "" + +#: i2p2www/pages/site/about/team.html:87 +msgid "gather, prioritize, advocate for user needs" +msgstr "" + +#: i2p2www/pages/site/about/team.html:90 +msgid "Web Designer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:92 +msgid "manage the public project website content design" +msgstr "" + +#: i2p2www/pages/site/about/team.html:95 +#, python-format +msgid "Webserver admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:97 +msgid "manage the public project webservers" +msgstr "" + +#: i2p2www/pages/site/about/team.html:100 +#, python-format +msgid "Website admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:102 +msgid "manage the public project website content" +msgstr "" + +#: i2p2www/pages/site/about/team.html:105 +msgid "News Admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:107 +msgid "manage router console news feed" +msgstr "" + +#: i2p2www/pages/site/about/team.html:110 +msgid "Director of passion" +msgstr "" + +#: i2p2www/pages/site/about/team.html:112 +msgid "community motivator" +msgstr "" + +#: i2p2www/pages/site/about/team.html:116 +msgid "Dev" +msgstr "" + +#: i2p2www/pages/site/about/team.html:117 +msgid "Core Lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:119 +msgid "lead dev for the SDK and router" +msgstr "" + +#: i2p2www/pages/site/about/team.html:122 +#, python-format +msgid "I2P mail lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:124 +msgid "organize and develop the i2p mail system" +msgstr "" + +#: i2p2www/pages/site/about/team.html:127 +#, python-format +msgid "I2Host lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:129 +msgid "I2Host addressbook application" +msgstr "" + +#: i2p2www/pages/site/about/team.html:132 +#, python-format +msgid "BOB lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:134 +msgid "Basic Open Bridge" +msgstr "" + +#: i2p2www/pages/site/about/team.html:137 +#, python-format +msgid "I2P-Bote lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:139 +msgid "I2PBote plugin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:142 +#, python-format +msgid "Robert lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:144 +msgid "Robert BitTorrent client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:147 +#, python-format +msgid "I2Phex lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:149 +msgid "I2Phex Gnutella client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:152 +#, python-format +msgid "I2PSnark lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:154 +msgid "Maintains the integrated Bittorrent client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:157 +#, python-format +msgid "iMule lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:159 +msgid "eMule client over I2P" +msgstr "" + +#: i2p2www/pages/site/about/team.html:162 +#, python-format +msgid "Syndie lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:164 +msgid "Syndie development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:167 +msgid "Susimail lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:169 +msgid "Susimail development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:172 +msgid "Console" +msgstr "" + +#: i2p2www/pages/site/about/team.html:174 +msgid "Router console HTML/CSS design" +msgstr "" + +#: i2p2www/pages/site/about/team.html:177 +msgid "SAM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:179 +msgid "SAM maintainer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:182 +msgid "I2PCPP lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:184 +msgid "C++ Router" +msgstr "" + +#: i2p2www/pages/site/about/team.html:187 +msgid "Translators" +msgstr "" + +#: i2p2www/pages/site/about/team.html:188 +msgid "many many people!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:193 +msgid "Contributors" +msgstr "" + +#: i2p2www/pages/site/about/team.html:195 +msgid "fire2pe dev, console enhancements" +msgstr "" + +#: i2p2www/pages/site/about/team.html:199 +msgid "desktopgui, dijjer port" +msgstr "" + +#: i2p2www/pages/site/about/team.html:203 +msgid "Debian/Ubuntu Packager and PPA maintainer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:207 +msgid "Routerconsole backend and UI work, website revamp, unit tests work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:212 +msgid "Help needed on many fronts!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:216 +msgid "Past contributors" +msgstr "" + +#: i2p2www/pages/site/about/team.html:218 +msgid "I2PTunnel development, ministreaming library" +msgstr "" + +#: i2p2www/pages/site/about/team.html:222 +msgid "Project lead, Syndie lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:226 +msgid "Project lead, Syndie lead, I2Phex, support guru" +msgstr "" + +#: i2p2www/pages/site/about/team.html:230 +msgid "iMule lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:234 +#: i2p2www/pages/site/about/team.html:238 +#: i2p2www/pages/site/about/team.html:242 +msgid "I2Phex work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:246 +msgid "Python SAM library, attack simulations" +msgstr "" + +#: i2p2www/pages/site/about/team.html:250 +msgid "i2pmail development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:254 +msgid "Syndie help" +msgstr "" + +#: i2p2www/pages/site/about/team.html:258 +msgid "i2p mail,susimail and susidns apps" +msgstr "" + +#: i2p2www/pages/site/about/team.html:262 +msgid "I2Phex (port of Phex to I2P)" +msgstr "" + +#: i2p2www/pages/site/about/team.html:266 +msgid "addressbook,i2p-bt,syndie client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:270 +msgid "organize and develop the i2p-bt BitTorrent port" +msgstr "" + +#: i2p2www/pages/site/about/team.html:274 +msgid "addressbook, i2p-bt, syndie client development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:278 +msgid "encryption and signature routines, I2PIM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:282 +msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)" +msgstr "" + +#: i2p2www/pages/site/about/team.html:286 +msgid "installer, systray, bogobot" +msgstr "" + +#: i2p2www/pages/site/about/team.html:290 +msgid "jbigi development, wiki migration, doc cleanup" +msgstr "" + +#: i2p2www/pages/site/about/team.html:294 +msgid "java debugging and client development on I2PTunnel and the router console" +msgstr "" + +#: i2p2www/pages/site/about/team.html:298 +msgid "SAM perl module" +msgstr "" + +#: i2p2www/pages/site/about/team.html:302 +msgid "i2psnark work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:306 +msgid "java cleanup" +msgstr "" + +#: i2p2www/pages/site/about/team.html:310 +msgid "docs. wiki migration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:314 +msgid "translations into French" +msgstr "" + +#: i2p2www/pages/site/about/team.html:318 +msgid "C port of jcpuid" +msgstr "" + +#: i2p2www/pages/site/about/team.html:322 +msgid "C# SAM library, pants, fortuna integration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:326 +msgid "libSAM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:330 +#: i2p2www/pages/site/about/team.html:334 +msgid "i2p-bt tracker development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:338 +msgid "Console and website themes" +msgstr "" + +#: i2p2www/pages/site/about/team.html:368 +msgid "… and many others" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:2 +msgid "Future Performance Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:4 +msgid "August 2010" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:7 +msgid "" +"There are a few major techniques that can be done to improve the " +"perceived\n" +"performance of I2P - some of the following are CPU related, others " +"bandwidth\n" +"related, and others still are protocol related. However, all of those\n" +"dimensions affect the latency, throughput, and perceived performance of " +"the\n" +"network, as they reduce contention for scarce resources. This list is of" +" course\n" +"not comprehensive, but it does cover the major ones that are seen." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:15 +#: i2p2www/pages/site/about/performance/index.html:106 +#, python-format +msgid "" +"For past performance improvements see the \n" +"Performance History." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:20 +msgid "Better peer profiling and selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:21 +#, python-format +msgid "" +"Probably one of the most important parts of getting faster performance " +"will\n" +"be improving how routers choose the peers that they build their tunnels " +"through\n" +"- making sure they don't use peers with slow links or ones with fast " +"links that\n" +"are overloaded, etc. In addition, we've got to make sure we don't expose" +"\n" +"ourselves to a Sybil attack\n" +"from a powerful adversary with lots of fast machines." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:30 +msgid "Network database tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:31 +msgid "" +"We're going to want to be more efficient with the network database's " +"healing\n" +"and maintenance algorithms - rather than constantly explore the keyspace " +"for new\n" +"peers - causing a significant number of network messages and router load " +"- we\n" +"can slow down or even stop exploring until we detect that there's " +"something new\n" +"worth finding (e.g. decay the exploration rate based upon the last time " +"someone\n" +"gave us a reference to someone we had never heard of). We can also do " +"some\n" +"tuning on what we actually send - how many peers we bounce back (or even " +"if we\n" +"bounce back a reply), as well as how many concurrent searches we perform." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:42 +msgid "Session Tag Tuning and Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:43 +#, python-format +msgid "" +"The way the ElGamal/AES+SessionTag " +"algorithm\n" +"works is by managing a set of random one-time-use 32 byte arrays, and " +"expiring\n" +"them if they aren't used quickly enough. If we expire them too soon, " +"we're\n" +"forced to fall back on a full (expensive) ElGamal encryption, but if we " +"don't\n" +"expire them quickly enough, we've got to reduce their quantity so that we" +" don't\n" +"run out of memory (and if the recipient somehow gets corrupted and loses " +"some\n" +"tags, even more encryption failures may occur prior to detection). With " +"some\n" +"more active detection and feedback driven algorithms, we can safely and " +"more\n" +"efficiently tune the lifetime of the tags, replacing the ElGamal " +"encryption with\n" +"a trivial AES operation." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:55 +#, python-format +msgid "" +"Additional ideas for improving Session Tag delivery are described on the\n" +"ElGamal/AES+SessionTag page." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:61 +msgid "Migrate sessionTag to synchronized PRNG" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:62 +#, python-format +msgid "" +"Right now, our ElGamal/AES+SessionTag \n" +"algorithm works by tagging each encrypted message with a unique random \n" +"32 byte nonce (a \"session tag\"), identifying that message as being " +"encrypted \n" +"with the associated AES session's key. This prevents peers from " +"distinguishing \n" +"messages that are part of the same session, since each message has a " +"completely \n" +"new random tag. To accomplish this, every few messages bundle a whole \n" +"new set of session tags within the encrypted message itself, " +"transparently \n" +"delivering a way to identify future messages. We then have to keep track" +" \n" +"of what messages are successfully delivered so that we know what tags \n" +"we may use." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:74 +msgid "" +"This works fine and is fairly robust, however it is inefficient in terms" +" \n" +"of bandwidth usage, as it requires the delivery of these tags ahead of \n" +"time (and not all tags may be necessary, or some may be wasted, due to \n" +"their expiration). On average though, predelivering the session tag costs" +" \n" +"32 bytes per message (the size of a tag). As Taral suggested though, that" +" \n" +"size can be avoided by replacing the delivery of the tags with a " +"synchronized \n" +"PRNG - when a new session is established (through an ElGamal encrypted \n" +"block), both sides seed a PRNG for use and generate the session tags on \n" +"demand (with the recipient precalculating the next few possible values \n" +"to handle out of order delivery)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:87 +msgid "Longer lasting tunnels" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:88 +msgid "" +"The current default tunnel duration of 10 minutes is fairly arbitrary, " +"though\n" +"it \"feels okay\". Once we've got tunnel healing code and more effective" +" failure\n" +"detection, we'll be able to more safely vary those durations, reducing " +"the\n" +"network and CPU load (due to expensive tunnel creation messages)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:95 +msgid "" +"This appears to be an easy fix for high load on the big-bandwidth " +"routers, but\n" +"we should not resort to it until we've tuned the tunnel building " +"algorithms further.\n" +"However, the 10 minute tunnel lifetime is hardcoded in quite a few " +"places,\n" +"so substantial effort would be required to change the duration.\n" +"Also, it would be difficult to maintain backward compatibility with such " +"a change." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:102 +msgid "" +"Currently, since the network average tunnel build success rate is fairly " +"high,\n" +"there are no current plans to extend tunnel lifetime." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:108 +msgid "Adjust the timeouts" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:109 +msgid "" +"Yet another of the fairly arbitrary but \"okay feeling\" things we've got" +" are the\n" +"current timeouts for various activities. Why do we have a 60 second " +"\"peer\n" +"unreachable\" timeout? Why do we try sending through a different tunnel " +"that a\n" +"LeaseSet advertises after 10 seconds? Why are the network database " +"queries\n" +"bounded by 60 or 20 second limits? Why are destinations configured to " +"ask for a\n" +"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a " +"peer to\n" +"reply to our request that they join a tunnel? Why do we consider a " +"tunnel that\n" +"doesn't pass our test within 60 seconds \"dead\"?" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:119 +msgid "" +"Each of those imponderables can be addressed with more adaptive code, as " +"well\n" +"as tunable parameters to allow for more appropriate tradeoffs between\n" +"bandwidth, latency, and CPU usage." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:125 +msgid "Full streaming protocol improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:128 +msgid "" +"Perhaps re-enable the interactive stream profile (the \n" +"current implementation only uses the bulk stream profile)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:134 +msgid "" +"Client level bandwidth limiting (in either or both directions on a " +"stream, \n" +"or possibly shared across multiple streams). This would be in addition to" +" \n" +"the router's overall bandwidth limiting, of course." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:141 +msgid "" +"Access control lists (only allowing streams to or from certain other " +"known \n" +"destinations)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:147 +msgid "" +"Web controls and monitoring the health of the various streams, as well \n" +"as the ability to explicitly close or throttle them." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:153 +#, python-format +msgid "" +"Additional ideas for improving the streaming library are described on the" +"\n" +"streaming library page." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:2 +msgid "Performance History" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:4 +#, python-format +msgid "" +"Notable performance improvements have been made using the techniques " +"below.\n" +"There is more to do, see the Performance " +"page\n" +"for current issues and thoughts." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:10 +msgid "Native math" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:11 +#: i2p2www/pages/site/about/performance/history.html:67 +#: i2p2www/pages/site/about/performance/history.html:82 +#: i2p2www/pages/site/about/performance/history.html:105 +#: i2p2www/pages/site/about/performance/history.html:133 +msgid "implemented" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:12 +#, python-format +msgid "" +"When I last profiled the I2P code, the vast majority of time was spent " +"within\n" +"one function: java.math.BigInteger's\n" +"modPow.\n" +"Rather than try to tune this method, we'll call out to\n" +"GNU MP - an insanely fast math library\n" +"(with tuned assembler for many architectures). (Editor: see\n" +"NativeBigInteger for faster public key " +"cryptography)" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:23 +msgid "" +"\n" +"ugha and duck are working on the C/JNI glue code, and the existing java " +"code\n" +"is already deployed with hooks for that whenever its ready. Preliminary " +"results\n" +"look fantastic - running the router with the native GMP modPow is " +"providing over\n" +"a 800% speedup in encryption performance, and the load was cut in " +"half. This\n" +"was just on one user's machine, and things are nowhere near ready for " +"packaging\n" +"and deployment, yet." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:32 +msgid "Garlic wrapping a \"reply\" LeaseSet" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:33 +msgid "implemented but needs tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:34 +msgid "" +"This algorithm tweak will only be relevant for applications that want " +"their\n" +"peers to reply to them (though that includes everything that uses " +"I2PTunnel or\n" +"mihi's ministreaming lib):" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:39 +msgid "" +"Previously, when Alice sent Bob a message, when Bob replied he had to do " +"a\n" +"lookup in the network database - sending out a few requests to get " +"Alice's\n" +"current LeaseSet. If he already has Alice's current LeaseSet, he can " +"instead\n" +"just send his reply immediately - this is (part of) why it typically " +"takes a\n" +"little longer talking to someone the first time you connect, but " +"subsequent\n" +"communication is faster. Currently - for all clients - we wrap\n" +"the sender's current LeaseSet in the garlic that is delivered to the " +"recipient,\n" +"so that when they go to reply, they'll always have the LeaseSet " +"locally\n" +"stored - completely removing any need for a network database lookup on " +"replies.\n" +"This trades off a large portion of the sender's bandwidth for that faster" +" reply.\n" +"If we didn't do this very often,\n" +"overall network bandwidth usage would decrease, since the recipient " +"doesn't\n" +"have to do the network database lookup." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:54 +msgid "" +"For unpublished LeaseSets such as \"shared clients\", this is the only " +"way to\n" +"get the LeaseSet to Bob. Unfortunately this bundling every time adds\n" +"almost 100% overhead to a high-bandwidth connection, and much more to" +"\n" +"a connection with smaller messages." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:60 +msgid "" +"Changes scheduled for release 0.6.2 will bundle the LeaseSet only when\n" +"necessary, at the beginning of a connection or when the LeaseSet changes." +"\n" +"This will substantially reduce the total overhead of I2P messaging." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:66 +msgid "More efficient TCP rejection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:68 +msgid "" +"At the moment, all TCP connections do all of their peer validation after\n" +"going through the full (expensive) Diffie-Hellman handshaking to " +"negotiate a\n" +"private session key. This means that if someone's clock is really wrong," +" or\n" +"their NAT/firewall/etc is improperly configured (or they're just running " +"an\n" +"incompatible version of the router), they're going to consistently " +"(though not\n" +"constantly, thanks to the banlist) cause a futile expensive cryptographic" +"\n" +"operation on all the peers they know about. While we will want to keep " +"some\n" +"verification/validation within the encryption boundary, we'll want to " +"update the\n" +"protocol to do some of it first, so that we can reject them cleanly\n" +"without wasting much CPU or other resources." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:81 +msgid "Adjust the tunnel testing" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:83 +msgid "" +"Rather than going with the fairly random scheme we have now, we should " +"use a\n" +"more context aware algorithm for testing tunnels. e.g. if we already " +"know its\n" +"passing valid data correctly, there's no need to test it, while if we " +"haven't\n" +"seen any data through it recently, perhaps its worthwhile to throw some " +"data its\n" +"way. This will reduce the tunnel contention due to excess messages, as " +"well as\n" +"improve the speed at which we detect - and address - failing tunnels." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:92 +msgid "Persistent Tunnel / Lease Selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:93 +msgid "" +"Outbound tunnel selection implemented in 0.6.1.30, inbound lease " +"selection \n" +"implemented in release 0.6.2." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:97 +msgid "" +"Selecting tunnels and leases at random for every message creates a large" +" \n" +"incidence of out-of-order delivery, which prevents the streaming lib from" +" \n" +"increasing its window size as much as it could. By persisting with the \n" +"same selections for a given connection, the transfer rate is much faster." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:104 +msgid "Compress some data structures" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:106 +msgid "" +"The I2NP messages and the data they contain is already defined in a " +"fairly\n" +"compact structure, though one attribute of the RouterInfo structure is " +"not -\n" +"\"options\" is a plain ASCII name = value mapping. Right now, we're " +"filling it\n" +"with those published statistics - around 3300 bytes per peer. Trivial to" +"\n" +"implement GZip compression would nearly cut that to 1/3 its size, and " +"when you\n" +"consider how often RouterInfo structures are passed across the network, " +"that's\n" +"significant savings - every time a router asks another router for a " +"networkDb\n" +"entry that the peer doesn't have, it sends back 3-10 RouterInfo of them." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:117 +msgid "Update the ministreaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:118 +msgid "replaced by full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:119 +msgid "" +"Currently mihi's ministreaming library has a fairly simple stream " +"negotiation\n" +"protocol - Alice sends Bob a SYN message, Bob replies with an ACK " +"message, then\n" +"Alice and Bob send each other some data, until one of them sends the " +"other a\n" +"CLOSE message. For long lasting connections (to an IRC server, for " +"instance),\n" +"that overhead is negligible, but for simple one-off request/response " +"situations\n" +"(an HTTP request/reply, for instance), that's more than twice as many " +"messages as\n" +"necessary. If, however, Alice piggybacked her first payload in with the " +"SYN\n" +"message, and Bob piggybacked his first reply with the ACK - and perhaps " +"also\n" +"included the CLOSE flag - transient streams such as HTTP requests could " +"be\n" +"reduced to a pair of messages, instead of the " +"SYN+ACK+request+response+CLOSE." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:132 +msgid "Implement full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:134 +msgid "" +"The ministreaming protocol takes advantage of a poor design decision in " +"the\n" +"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", " +"allowing what\n" +"would otherwise be an unreliable, best-effort, message based protocol to " +"be used\n" +"for reliable, blocking operation (under the covers, its still all " +"unreliable and\n" +"message based, with the router providing delivery guarantees by garlic " +"wrapping\n" +"an \"ACK\" message in with the payload, so once the data gets to the " +"target, the\n" +"ACK message is forwarded back to us [through tunnels, of course])." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:143 +#, python-format +msgid "" +"As I've said, having\n" +"I2PTunnel (and the ministreaming lib) go this route was the best thing " +"that\n" +"could be done, but more efficient mechanisms are available. When we rip " +"out the\n" +"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves " +"with an\n" +"I2CP that looks like an anonymous IP layer, and as such, we'll be able to" +"\n" +"implement the streaming library to take advantage of the design " +"experiences of\n" +"the TCP layer - selective ACKs, congestion detection, nagle, etc." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:2 +msgid "Performance" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:5 +msgid "" +"How does I2P work, why is it slow, and why does it not use my full " +"bandwidth?" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:7 +msgid "" +"Probably one of the most frequent things people ask is \"how fast is " +"I2P?\",\n" +"and no one seems to like the answer - \"it depends\". After trying out " +"I2P, the\n" +"next thing they ask is \"will it get faster?\", and the answer to that is" +" a most\n" +"emphatic yes." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:14 +msgid "" +"I2P is a full dynamic network. Each client is known to other nodes and " +"tests local known nodes for reachability and capacity.\n" +"Only reachable and capable nodes are saved to a local NetDB (This is " +"generally only a portion of the network, around 500-1000).\n" +"When I2P builds tunnels, it selects the best resource from this pool. For" +" example, a small subset of 20-50 nodes are only available to build " +"tunnels with.\n" +"Because testing happens every minute, the pool of used nodes changes " +"every minute.\n" +"Each I2P node knows a different part of the net, meaning that each router" +" has a different set of I2P nodes to be used for tunnels.\n" +"Even if two routers have the same subset of known nodes, the tests for " +"reachability and capacity will likely show different results, as the " +"other routers could be under load just as one router tests, but be free " +"if the second router tests." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:23 +msgid "" +"The above describes why each I2P node has different nodes to build " +"tunnels.\n" +"Because every I2P node has a different latency and bandwith, tunnels " +"(which are built via those nodes) have different latency and bandwidth " +"values.\n" +"And because every I2P node has different tunnels built, no two I2P nodes " +"have the same tunnel sets." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:29 +msgid "" +"A server/client is known as a \"destination\" and each destination has at" +" least one inbound and one outbound tunnel. The default is 3 hops per " +"tunnel.\n" +"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip" +" client-server-client." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:34 +msgid "" +"Each data package is sent through 6 other I2P nodes until it reaches the " +"server:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:40 +msgid "and on way back 6 different I2P nodes:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:47 +msgid "" +"As most traffic on I2P (www, torrent,...) needs ack packages until new " +"data is sent, it needs to wait until a ack package returns from the " +"server.\n" +"In the end: send data, wait for ack, send more data, wait for ack,..\n" +"As the RTT (RoundTripTime) adds up from the latency of each individual " +"I2P node and each connection on this roundtrip, it takes usually 1-3 " +"seconds until a ack package comes back to the client.\n" +"With some internals of TCP and I2P transport, a data package has a " +"limited size and cannot be as large as we want it to be.\n" +"Together these conditions set a limit of max bandwidth per tunnel of " +"20-50 kbyte/sec.\n" +"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, " +"the whole tunnel is limited to 5 kb/sec, independent of the \n" +"latency and other limitations." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:57 +msgid "" +"Due to encryption used and other setups in I2P (howto built up tunnels, " +"latency, ...) it is quite expensive in CPU time to build a tunnel. This " +"is \n" +"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels" +" to transport data. With a max of 50 kb/sec per tunnel, a destination " +"could \n" +"use roughly 300 kb/sec traffic combined ( in reality it could be more if " +"shorter tunnels are used with low or no anonymity available).\n" +"Used tunnels are discarded every 10 minutes and new ones are built up.\n" +"This change of tunnels (and sometimes clients that shutdown hard due to " +"usage of \"shut down at once\" or situations where there is power loss) " +"does \n" +"sometimes break tunnels and connections, as seen on the IRC2P Network in " +"loss of connection (ping timeout) or on when using eepget." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:66 +msgid "" +"With a limited set of destinations and a limited set of tunnels per " +"destination, one I2P node only uses a limited set of tunnels across other" +" I2P nodes.\n" +"For example, if an I2P node is \"hop1\" in the small example above, we " +"only see 1 participating tunnel originating from the client.\n" +"If we sum up the whole I2P network, only a rather limited number of " +"participating tunnels could be built with a limited amount of bandwidth " +"all together.\n" +"If one distributes these limited numbers across the number of I2P nodes, " +"there is only a fraction of available bandwidth/capacity available for " +"use." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:73 +msgid "" +"To remain anonymous one router should not be used by the whole network " +"for building tunnels.\n" +"If one router does act as a tunnel router for ALL I2P nodes, it becomes a" +" very real central point of failure as well as a central point to grab " +"IPs and data from the clients. This is not good.\n" +"I2P attempts to spread the load across a lot of I2P nodes because of this" +" reason." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:79 +msgid "" +"Another point is the full mesh network. Each connection hop-hop utilizes " +"one TCP or UDP connection on the I2P nodes. With 1000 connections, one " +"sees \n" +"1000 TCP connections. That is quite a lot and some home and small office " +"routers (DSL, cable,..) only allow a small number of connections (or just" +" go mad if you use more than X connections).\n" +"I2P tries to limit these connections to be under 1500 per UDP and per TCP" +" type.\n" +"This limits the amount of traffic routed across your I2P node as well." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:86 +msgid "" +"In summary, I2P is very complex and there is no easy way to pinpoint why " +"your node is not used.\n" +"If your node is reachable and has a bandwidth setting of >128 kbyte/sec " +"shared and is reachable 24/7, it should be used after some time for " +"participating traffic.\n" +"If it is down in between, the testing of your I2P node done by other " +"nodes will tell them: you are not reachable. This blocks your node for at" +" least \n" +"24h on other nodes. So, the other nodes which tested you as down will not" +" use your node for 24h for building tunnels. This is why your traffic " +"will \n" +"be lower after a restart/shutdown for a minimum of 24h." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:94 +msgid "" +"Also: other I2P nodes needs to know your I2P router to test it for " +"reachability and capacity. It takes time for other nodes to get known to " +"your node. \n" +"It will be faster if you use I2P and build more tunnels, e.g. use a " +"torrent or www for some time." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:99 +msgid "Performance Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:101 +#, python-format +msgid "" +"For possible future performance improvements see\n" +"Future Performance Improvements." +msgstr "" + diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/misc.po b/i2p2www/translations/pt_BR/LC_MESSAGES/misc.po new file mode 100644 index 00000000..9ed8e4b2 --- /dev/null +++ b/i2p2www/translations/pt_BR/LC_MESSAGES/misc.po @@ -0,0 +1,1232 @@ +# Portuguese (Brazil) translations for I2P. +# Copyright (C) 2013 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# blueboy, 2013 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2013-08-30 23:32+0000\n" +"PO-Revision-Date: 2013-12-19 13:27+0000\n" +"Last-Translator: blueboy\n" +"Language-Team: Portuguese (Brazil) " +"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 0.9.6\n" + +#: i2p2www/pages/site/misc/clt.html:2 +msgid "I2P at CLT and PetCon 2009.1" +msgstr "" + +#: i2p2www/pages/site/misc/clt.html:4 +msgid "" +"Members of I2P will held a talk at CLT and PetCon 2009.1\n" +"Two members of the I2P team will be at two forthcoming Linux day and " +"security convention." +msgstr "" + +#: i2p2www/pages/site/misc/clt.html:9 +#, python-format +msgid "" +"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.\n" +"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!" +msgstr "" + +#: i2p2www/pages/site/misc/clt.html:14 +#, python-format +msgid "" +"Just 10 days later the Privacy and Data Security " +"convention in Dresden will take place.\n" +"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." +msgstr "" + +#: i2p2www/pages/site/misc/cvs.html:4 +#, python-format +msgid "" +"The I2P sourcecode was kept in a CVS repository. Nowadays it is kept in a" +" Monotone repository.\n" +"For those who aren't very familiar with CVS, there is a\n" +"fantastic book " +"on the\n" +"subject (developers only need to deal with the first chapter - \"An " +"Overview of\n" +"CVS\", as subsequent chapters go into some nasty details very few ever " +"need to\n" +"touch)." +msgstr "" + +#: i2p2www/pages/site/misc/cvs.html:31 +msgid "" +"Humorous quote from WinCVS: \"Did you know... Never experiment with new " +"CVS\n" +"commands on your working repository. Create a sample module instead.\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:2 +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:4 +msgid "I2PTunnel migration" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:6 +msgid "" +"After upgrading to the new architecture, you'll have to do a \n" +"little work to get your old I2PTunnel-driven servers running. \n" +"Lets walk through a simple example. For an eepsite with the \n" +"old clientApp configuration, you had:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:16 +msgid "To provide that same functionality on the new web architecture:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:18 +#, python-format +msgid "Jump to %(url)s" +msgstr "Pular para %(url)s" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:19 +msgid "Click on Add new: [Server tunnel] \"GO\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:21 +msgid "For the name: \"eepsite\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:22 +msgid "For the description: \"My eepsite, isn't it pretty?\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:23 +msgid ">For the target host:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:24 +msgid "For the target port:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:25 +msgid "" +"For the private key file: path to \"myWebPriv.dat\"
\n" +"(it is recommended to copy that .dat to your new install dir)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:29 +msgid "Check the \"Start automatically?\" checkbox" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:30 +msgid "Click \"Save\"" +msgstr "Clique em \"Salvar\"" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:32 +msgid "It will come back saying:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:39 +msgid "" +"That's it! Creating a new I2PTunnel server works the same way too, " +"except you\n" +"don't need to \"copy the old file\", obviously. Behind the scenes, it is" +" all driven\n" +"by the i2ptunnel.config file, which you may modify " +"externally (if you do,\n" +"hit \"Reload config\" on the I2PTunnel web page, which will tear down all" +" of your \n" +"existing tunnels and rebuild new ones)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:47 +msgid "" +"Note that you WILL need to wait until your router is integrated\n" +"into the network before you are able to use the /i2ptunnel/ web\n" +"interface. It will say \"Please be patient\" if you try to \n" +"beforehand, which means that it is still trying to build the \n" +"necessary I2PTunnel sessions it has been configured to create." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:2 +msgid "I2PTunnel services" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:4 +msgid "Below is quick copy of aum's eepsite deployment guide." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:8 +msgid "1. - Deploy a local server" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:10 +msgid "" +"For simplicity's sake, we will walk through the setup of a web server; " +"however, this procedure is the same regardless what protocol of servers " +"and/or clients you are setting up." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:13 +msgid "" +"I recommend the Tiny Httpd web server, thttpd, (windows version available" +" on site) although you can use anything that you feel comfortable with." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:16 +msgid "" +"Another more robust option would be to use EasyPHP, which is also open " +"source. It comes with PHP, PHPmyadmin, mySQL, and Apache web server. For " +"newbies who have no experience setting up and hosting content over " +"servers, see the hosting page for help." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:19 +msgid "" +"With the web server you've chosen, configure it to listen on a port of " +"your choice, and serve its documents from a directory of your choice. For" +" this example, we'll assume port 10880." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:22 +msgid "" +"Make sure your firewall is set up so that you cannot receive incoming " +"connections on this port (which would breach your anonymity)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:25 +msgid "" +"Test the webserver, by pointing your normal browser (the one with the " +"\"direct connection\") at http://localhost:10880 (changing the 10880 to the " +"port number you have chosen)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:28 +msgid "" +"Once your webserver is working, and you can access it locally with your " +"browser, continue to the next step." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:33 +msgid "2 - Generate an I2P Destination Keypair" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:35 +msgid "" +"I2P does not deal in IP addresses. To protect your anonymity, it deals in" +" unique addresses called destination keys." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:38 +msgid "" +"A destination key works a lot like a regular IP address, except that it " +"can't be traced to your IP address or physical location. When users place" +" a request to speak with you, your gateways are the ones that answer for " +"you. So the requesting user can only know the IP address of your " +"gateways. However, gateways don't know your IP address, because gateways " +"are the last nodes on your tunnels, and you anonymously create tunnels by" +" way of garlic routing. (So gateways are like puppets that can't see " +"their masters, and everyone communicates through these puppets)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:41 +msgid "" +"To deploy a server on I2P, you create a destination keypair. You use the " +"private key to authenticate your server when connecting it to I2P, and " +"you make the public key (aka destination key) known publicly, so others " +"can connect to your server. (indirectly, through your gateways)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:44 +msgid "Each service you run on I2P requires a different keypair." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:47 +msgid "" +"To generate your keypair, type the command: java -jar " +"lib/i2ptunnel.jar -nogui -e \"genkeys myWebPrivKey.dat " +"myWebPubKey.dat\" (all on one line)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:50 +msgid "" +"In windows, to generate your keypair, type the command: java -jar " +"lib/i2ptunnel.jar -nogui -e \"genkeys myWebPrivKey.dat " +"myWebPubKey.dat\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:53 +msgid "" +"The filenames myWebPrivKey.dat and " +"myWebPubKey.dat are arbitrary - choose whatever you want " +"here, as long as you understand your own choices." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:56 +msgid "" +"We now need to export your public key into base64 format, which you will " +"share with others." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:59 +msgid "" +"To convert your myWebPubKey.dat file into shareable base64, type the " +"command java -cp lib/i2p.jar net.i2p.data.Base64 encode " +"myWebPubKey.dat > myWebPubKey.txt (all on one line)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:62 +msgid "" +"This file you have just generated, myWebPubKey.txt, contains" +" a long base64 string (516 chars at last count), which we call a " +"destination key. All you need to know about this string for now is that " +"it allows remote clients to uniquely pinpoint and connect to your server," +" just the same way as an IP address allows remote machines to pinpoint " +"and connect to your machine." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:65 +msgid "" +"However, in contrast to an IP address, there is no way to trace your " +"machine's physical location - even though your server can be addressed " +"via I2P, your IP address cannot be traced or associated with this " +"destination key." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:70 +msgid "3 - Open a 'Tunnel' from I2P To Your Server" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:72 +msgid "" +"For clients elsewhere in I2P to be able to access your server, you must " +"run a 'bridge' or 'tunnel', which takes connections from these clients " +"and forwards them to your local server." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:75 +msgid "" +"To activate such a tunnel, type the command java -jar " +"lib/i2ptunnel.jar -nogui -e \"server localhost 10880 " +"myWebPrivKey.dat\" (all one line)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:78 +msgid "" +"If you used different filenames or port number earlier on, change these " +"accordingly" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:81 +msgid "" +"Windows users, remember to replace apostrophes with double quotes. Thus: " +"java -jar lib/i2ptunnel.jar -nogui -e \"server localhost 10880 " +"myWebPrivKey.dat\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:84 +msgid "" +"Within a few seconds, the 'tunnel' should now be active, and remote " +"clients should be able to reach your server anonymously. Remember to let " +"your router \"warm up\" before opening clients to it." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:89 +msgid "4 - Update Your hosts.txt File " +msgstr "4 - Atualizar o seu arquivo hosts.txt" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:91 +msgid "" +"To test your own server locally, you'll need to create an entry in your " +"hosts.txt file, so I2P can translate the simple URL you place in the " +"browser's address bar into the full public key text needed to find your " +"server." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:94 +msgid "" +"Edit your hosts.txt, and add the line myserver.i2p=blahblahblah, where " +"myserver.i2p is an I2P 'domain' you want to associate with your site, and" +" the blahblahblah is the text of the base64 public key you created " +"earlier in the file myWebPubKey.txt" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:97 +msgid "" +"With this in place, you and others can reach your server with the simple " +"domain name myserver.i2p in the browser's address bar." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:102 +msgid "5 - Surf Your Site Within I2P" +msgstr "5 - Navegar pelo seu site na I2P" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:104 +msgid "" +"Using your secondary browser - the one you earlier configured to use " +"localhost:4444 as a proxy - point this browser to the address http://myserver.i2p" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:107 +msgid "You should see the main page of your webserver come up." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:112 +msgid "6 - Create a Local Client Tunnel Connection " +msgstr "6 - Criar uma conexão tunelada para um cliente local" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:114 +msgid "We now have to think beyond just web servers." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:117 +msgid "" +"As you grow into I2P and get more of a 'feel' for it, you will want to " +"use all manner of servers and clients." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:120 +msgid "" +"The beauty of I2P is that it allows standard Internet clients and servers" +" for most protocols to be transparently 'tunneled' through the anonymous " +"network." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:123 +msgid "" +"You can run mailservers/clients, nameservers/clients, newsservers/clients" +" - almost anything at all - perhaps even FTP in passive mode." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:126 +msgid "" +"Now, we'll create a client tunnel. This is like the server tunnel we " +"created earlier, but works in reverse. It listens to a port on your local" +" machine; your local client connects to this port; the connection gets " +"forwarded through I2P to the service on the other end." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:129 +msgid "" +"To open your client tunnel for your server, type the command java " +"-jar lib/i2ptunnel.jar -nogui -e \"config localhost 7654\" -e \"client " +"10888 textofbase64key\" (all one line)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:132 +msgid "" +"The port 10888 is arbitrary - it just needs to be something other than " +"the physical port your server is listening on." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:135 +msgid "" +"textofbase64key is simply the contents of the public key text file " +"myWebPubKey.txt, reproduced fully on one line (alternately, instead of " +"textofbase64key, you can specify the name from your hosts.txt - e.g. " +"myserver.i2p)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:138 +msgid "" +"Within a minute or two of launching this command, the client tunnel from " +"your local machine into I2P will be open and ready for use." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:141 +msgid "" +"Point your regular web browser (ie, not the one you configured to use " +"localhost:4444), and point it to http://localhost:10888" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:144 +msgid "" +"Verify that the main page of your server eventually comes up in your " +"browser." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:147 +msgid "" +"You use the same procedure for using any local client program to access a" +" remote I2P server - just get the base64 public key (called destination " +"key) of the remote server, choose a local port to connect to the remote " +"server, open the tunnel, and just connect with your client to your " +"heart's content." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:152 +msgid "7 - Share your server details with others" +msgstr "7 - Compartilhar os detalhes do seu servidor com terceiros" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:154 +msgid "" +"Using an anonymous medium (eg the one of the I2P IRC servers or ugha's " +"wiki), post your domain name (eg www.mynick.i2p as well as your destination key. " +"Others will then be able to reach your server remotely, without either of" +" you jeopardizing your anonymity." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:157 +msgid "" +"Remember, you can go to What's on I2P and find the latest public keys " +"linked to their URL. You should also post your own public key and URL " +"their. However, you will want to do this anonymously, of course. " +"Drupal.i2p.net is currently, as of this writing, only accessible from the" +" net. So, to access the outside WWW anonymously from inside of I2P, you " +"will need to start up your script called startSquid. Do it the same way " +"you have been doing these other scripts. Reconfigure your browser to " +"proxy on localhost:5555, as defined in the script, and when the script " +"has generated it's keys, you can access the squid proxy. Put any WWW URL " +"(such as Google or this i2p site) into your browser's address bar and you" +" will be surfing the World Wide Web anonymously. Now you can safely post " +"your public key, and no one can detect your IP address." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:162 +msgid "8 - Write Some Scripts To Handle All This Menial Nonsense" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:164 +msgid "" +"It would drive most people crazy, going through all these steps every " +"time one sets up an I2P server, and/or deploys a client." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:167 +msgid "" +"Aum's website http://www.freenet.org.nz/i2p/ has a script called " +"setupServer.py which automates all this nonsense into one simple command " +"line . But I respect that people's tastes in user interfaces differ, and " +"trying to write something which satisfies everyone's needs usually " +"results in something so complex that it turns into newbie-repellent." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:170 +msgid "" +"So please feel free to use and/or customize setupServer.py to taste, or " +"write your own in Python or another language." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:173 +msgid "" +"Also, you may want to write a script which handles the startup of the I2P" +" Router, the eepProxy, plus any and all tunnels you are using. I've got " +"such a script called startEverything.sh, which gets launched at system " +"startup. (Be sure to search this site for template scripts to automate " +"your I2P commands. If I create a page for one, I'll try to remember to " +"link it here." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:176 +msgid "Exercise for Windows users - port setupServer.py into a MS-DOS .BAT file." +msgstr "" + +#: i2p2www/pages/site/misc/invisiblenet.html:2 +msgid "Old Documents" +msgstr "Documentos antigos" + +#: i2p2www/pages/site/misc/invisiblenet.html:5 +msgid "" +"Following is a list of documents originally on www.invisiblenet.net/i2p/ " +"and\n" +"rescued via the\n" +"Wayback Machine.\n" +"They are quite dated and may or may not be accurate.\n" +"However, the I2CP and I2NP documents in particular have some good " +"information." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:3 +msgid "August 2011" +msgstr "Agosto de 2011" + +#: i2p2www/pages/site/misc/jbigi.html:6 +msgid "Overview" +msgstr "Visão geral" + +#: i2p2www/pages/site/misc/jbigi.html:7 +msgid "" +"Using JNI (Java Native Interface), a bit of C code (thanks ugha!), a " +"little\n" +"manual work and a piece of chewing gum we have made several\n" +"cryptography operations quite a bit faster." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:13 +#, python-format +msgid "" +"The speedup comes from the super-fast\n" +"GNU MP Bignum library (libgmp).\n" +"We use a single function from libgmp -\n" +"mpz_powm()\n" +"as a replacement for the\n" +"Java Math library's BigInteger modPow().\n" +"As modPow() is a significant computational portion of many crypto " +"operations, this is of significant benefit." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:25 +#, python-format +msgid "" +"The standard I2P installation includes about 20 versions of the library " +"for different platforms,\n" +"each about 50KB, inside the jbigi.jar file.\n" +"The initialization of the JBigI library, including CPU identification, " +"selection, and extraction\n" +"of the correct loadable module, is handled by the\n" +"NativeBigInteger class.\n" +"If no module is available for the current platform, the standard\n" +"Java Math library's BigInteger modPow()\n" +"is used." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:38 +msgid "Rebuilding and Testing JBigI" +msgstr "Recompilando e testando a biblioteca JBigl" + +#: i2p2www/pages/site/misc/jbigi.html:39 +msgid "" +"Following are the instructions to build a new jbigi library for your own " +"platform\n" +"and testing its performance." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:42 +msgid "Requirements" +msgstr "Requerimentos" + +#: i2p2www/pages/site/misc/jbigi.html:43 +msgid "" +"This works on Linux, and with a few changes in build.sh probably also on\n" +"other platforms. FreeBSD has also been reported to work too. On Kaffee " +"the\n" +"speedup is very small, because it already uses native BitInteger " +"internally.\n" +"Blackdown seems to cause strange errors. Because you are going to do\n" +"compilation, you need JDK; JRE won't work." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:50 +msgid "" +"The required code is available in monotone database and the latest source" +" tarball. " +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:51 +msgid "" +"The GNU MP Bignum library (libgmp) needs to be installed, if it isn't\n" +"included in your OS / distribution or installed already, it can be " +"received from\n" +"http://gmplib.org/#DOWNLOAD. " +"Even if you\n" +"have already installed it as binary, it might still be worth a try to " +"compile\n" +"GMP yourself, since then it will be able to use the specific instructions" +" of\n" +"your processor. The latest GMP may also\n" +"be used instead of GMP 5.0.2, but it hasn't been tested by us." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:61 +msgid "Step-by-step instructions" +msgstr "Instruções passo-a-passo" + +#: i2p2www/pages/site/misc/jbigi.html:63 +msgid "" +"Look at your running " +"environment on the logs.jsp page.\n" +"There should be one of two status messages for JBigI - either" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:66 +msgid "Locally optimized native BigInteger loaded from the library path" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:68 +msgid "or" +msgstr "ou" + +#: i2p2www/pages/site/misc/jbigi.html:70 +msgid "Native BigInteger library jbigi not loaded - using pure java" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:71 +msgid "" +"If the native BitInteger library was NOT loaded, you definitely need to\n" +"compile your own.\n" +"Certain platforms, such as OS X, OpenSolaris, and 64-bit systems,\n" +"may require you to compile your own library.\n" +"If the BigInteger library was loaded, do at least the next step to see\n" +"what your performance is." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:78 +msgid "" +"Look on http://localhost:7657/stats.jsp" +"\n" +"to see what the lifetime average values for " +"crypto.elGamal.decrypt and\n" +"crypto.elGamal.encrypt are. The numbers are times in " +"milliseconds. Copy these somewhere so you can compare\n" +"them later on.\n" +"The network average for encrypt time is about 20ms.\n" +"If your encrypt time is less than 50ms for a relatively new processor, or" +" less than 100ms\n" +"for an older processor, and the native BigInteger library was loaded, you" +" are probably fine." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:87 +#, python-format +msgid "" +"Get the latest released source code of I2P from\n" +"the download page, or get the cutting-edge " +"source\n" +"out of the monotone database mtn.i2p2.de" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:92 +msgid "Inside the source tree change directory to: core/c/jbigi" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:93 +msgid "" +"Read the README file.\n" +"If you have a /usr/lib/libgmp.so file, you do not have to download GMP.\n" +"Use the 'dynamic' argument to build.sh.\n" +"Otherwise, you must download GMP version 5.0.2 from\n" +"from http://gmplib.org/#DOWNLOAD, " +"saving it to gmp-5.0.2.tar.bz2.\n" +"If you decide to use a newer version, change the VER= line in " +"core/c/jbigi/build.sh." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:101 +msgid "" +"Take a look at build.sh, if your JAVA_HOME\n" +"environment variable is set and you are using Linux then it might just " +"work.\n" +"Otherwise change the settings. Remember, you need the Java SDK installed." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:106 +msgid "" +"Run build.sh (if you downloaded GMP) or\n" +"build.sh dynamic (if you have /usr/lib/libgmp.so).
\n" +"Maybe the build spewed out some errors of missing jni.h and jni_md.h " +"files.\n" +"Either copy these files from your java install into the " +"core/c/jbigi/jbigi/include/ directory,\n" +"or fix $JAVA_HOME.
\n" +"You can run the build.sh from the core/c/ " +"directory which will\n" +"build all available jbigi libs into a jbigi.jar.
\n" +"A file named libjbigi.so should be created in the current\n" +"directory. If this doesn't happen and/or you get errors then please " +"report\n" +"them." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:118 +msgid "" +"Follow the instructions in core/c/README to install the library and run\n" +"the speed test.\n" +"Read the final lines of the speed test's output for some additional\n" +"info, it will be something like this:" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:128 +msgid "" +"If the native is indeed 5-7x faster (or more) then it looks all good. If " +"not, please report." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:129 +msgid "Copy libjbigi.so to your i2p directory" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:130 +msgid "Restart your I2P programs." +msgstr "Reinicializar os seus programas I2P" + +#: i2p2www/pages/site/misc/jbigi.html:131 +msgid "" +"On http://localhost:7657/stats.jsp" +"\n" +"the crypto.elGamal.decrypt and " +"crypto.elGamal.encrypt\n" +"should be a lot faster." +msgstr "" + +#: i2p2www/pages/site/misc/jrandom-awol.html:2 +msgid "Jrandom's Announcement" +msgstr "Comunicado do Jrandom" + +#: i2p2www/pages/site/misc/jrandom-awol.html:4 +msgid "" +"The following message was received in mid-November 2007. We have no " +"further information\n" +"on jrandom's status." +msgstr "" + +#: i2p2www/pages/site/misc/jrandom-awol.html:9 +#, python-format +msgid "" +"Subsequently, in an unrelated incident, the hosting company for\n" +"all *.i2p.net servers (except forum.i2p.net) suffered a power outage\n" +"on January 13, 2008, and the i2p.net servers did not fully return to " +"service.\n" +"As only jrandom has the credentials required to restore service,\n" +"and he could not be contacted,\n" +"we moved all public services to www.i2p2.de\n" +"and related subdomains." +msgstr "" + +#: i2p2www/pages/site/misc/jrandom-awol.html:19 +#, python-format +msgid "" +"Approximately two months later, for unrelated reasons,\n" +"forum.i2p.net was moved to %(forum)s." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:2 +#: i2p2www/pages/site/misc/manual-wrapper.html:4 +msgid "Manually Installing the Java Wrapper" +msgstr "Instalação manual do Empacotador Java" + +#: i2p2www/pages/site/misc/manual-wrapper.html:6 +#, python-format +msgid "" +"The installation package for the I2P router" +" comes\n" +"with a Java wrapper for the most common architectures. If your system is " +"not\n" +"supported by our installer—or if you want to update the wrapper to " +"a\n" +"newer version—the following steps describe installing the wrapper " +"manually." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:14 +msgid "" +"Check Tanuki Software's download" +" page\n" +"for your platform. Is your platform listed? If so, you're in\n" +"luck! Download the most recent version of the Community Edition for your " +"OS and\n" +"CPU and move to the next step." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:20 +msgid "" +"If your platform does not have an already compiled wrapper available, you" +"\n" +"may be able to compile it yourself. If you are willing to have a go at " +"it, move\n" +"on to compiling the wrapper for your system." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:27 +msgid "Using existing binaries" +msgstr "Usando os binários existentes" + +#: i2p2www/pages/site/misc/manual-wrapper.html:28 +msgid "In the steps below, $I2P means the location I2P was installed to." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:36 +#: i2p2www/pages/site/misc/manual-wrapper.html:64 +msgid "Try to start I2P using $I2P/i2prouter start" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:37 +#: i2p2www/pages/site/misc/manual-wrapper.html:65 +msgid "tail -f /tmp/wrapper.log and look for any problems." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:39 +#: i2p2www/pages/site/misc/manual-wrapper.html:67 +msgid "" +"If this did not work you'll need to use runplain.sh to start" +" I2P." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:43 +msgid "Compiling from source" +msgstr "Compilando apartir do código-fonte" + +#: i2p2www/pages/site/misc/manual-wrapper.html:44 +msgid "" +"These steps worked to compile the wrapper for use on a mipsel system " +"running Debian. The steps will need to be altered for " +"your system." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:48 +msgid "" +"Download the source archive for the community version of the wrapper from" +" wrapper download" +" page." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:49 +msgid "Extract the tarball" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:51 +msgid "" +"Set environment variables ANT_HOME and " +"JAVA_HOME. For example, in Debian:" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:54 +msgid "" +"Since there isn't a Makefile for Mipsel, we'll make a copy of an already " +"existing makefile:" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:56 +msgid "Now we can attempt to compile the wrapper:" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:57 +msgid "use ./build64.sh if you have a 64bit CPU and JVM" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:58 +msgid "Copy the wrapper into its proper place:" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:4 +msgid "" +"Here's an outline and rationale for a minimal WWW proxy app for use over " +"I2P." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:8 +msgid "" +"HTTP operation over I2P using I2PTunnel. When the base SocketLibrary\n" +"is out, the only significant difference will be the 'wrapRequest' and\n" +"'unwrapRequest' will functionally be placed in the socketLibrary, not\n" +"in the router (but later versions of the SocketLibrary will be able to\n" +"use selective ACK and large window sizes, allowing more ACKs to be\n" +"skipped)" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:47 +msgid "" +"An optimized form, designed to handle only 128KB [1] files and pages, can" +"\n" +"operate significantly faster:" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:71 +msgid "" +"The difference in network load and latency is significant - this is\n" +"essentially a UDP version of HTTP. On the normal web, we can't really do" +" that,\n" +"since most HTTP requests and responses are orders of magnitude larger " +"than UDP\n" +"packets functionally support, but in I2P, messages can be large. The " +"savings\n" +"for the network load comes from the fact that we don't need to send any " +"ACK\n" +"messages - rather than the earlier wrap/unwrap request (that bundles a\n" +"DataMessage with a DeliveryStatusMessage to provide guaranteed delivery)," +" the\n" +"MinWWW proxy deals with resends (if necessary - in I2PTunnel today, there" +" are no\n" +"resends)." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:83 +msgid "" +"The data that the MinWWW proxy and server need to wrap is trivial - when " +"the\n" +"proxy wants to send \"GET /\", it prepends it with the I2P Destination " +"sending\n" +"the request, followed by a 4 byte request ID. The MinWWW server receives" +" those\n" +"requests, contacts the appropriate HTTPD, sends the request, waits for " +"the\n" +"response, and sends a reply to the MinWWW proxy containing the response,\n" +"prefixed with the original request ID. That response is taken and passed" +" back\n" +"to the browser and the connection is closed." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:93 +msgid "" +"In addition, the MinWWW proxy can choose the MinWWW server to use from a\n" +"list, going through some round robin or other algorithm, so that there " +"are\n" +"multiple outproxies merged transparently. The bandwidth required for " +"running\n" +"one of these outproxies is also greatly reduced, since it will only " +"handle 128KB\n" +"files (aka no one is going to be downloading porn, warez, etc)." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:101 +msgid "" +"The functionality /is/ limited, but 128KB of data is a lot for a single " +"HTTP\n" +"request or response. The above diagrams are also unrealistic in their " +"hops -\n" +"ROUTERA will really never talk directly to ROUTERB. ROUTERA will send " +"each\n" +"of the messages through two additional outbound routers, then forwarded " +"to\n" +"two additional inbound routers to ROUTERB, so the lag there is " +"significant -\n" +"while the above only saves 11 steps, 8 of those steps need to traverse " +"the\n" +"entire tunnel path (4+ remote hops each time when tunnels are 2 remote " +"hops\n" +"in each stretch), leaving MinWWW with only two full traversals (one for " +"the\n" +"request, one for the response), instead of 10." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:113 +msgid "" +"Implementing the MinWWW proxy and server should be fairly easy - read an " +"HTTP\n" +"request from the client fully (perhaps only start out with HTTP GET, " +"leaving\n" +"HTTP POST for later), wrap the message, and wait for the response. The " +"server\n" +"in turn simply needs to parse the request to either open a socket or URL," +"\n" +"send the request, wait for the response, and send it back through the " +"network.\n" +"If someone were to implement this, it would be Good :)" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:122 +msgid "" +"[1] Why 128KB files? Currently I2CP allows functionally arbitrary " +"message\n" +"size, but that's going to be going away since it involves either " +"excessive memory\n" +"overhead on intermediary routers, or additional implementation details to" +"\n" +"handle. I2PTunnel is currently limited to 128KB and hasn't been a " +"burden,\n" +"so perhaps it could be increased to 256KB when the I2CP spec is updated)" +msgstr "" + +#: i2p2www/pages/site/misc/myi2p.html:4 +msgid "" +"There has been discussion about a distributed blogging application for a " +"few\n" +"months now called \"MyI2P\". While the original discussions were lost, " +"we were \n" +"able to retrieve a Google cache\n" +"of it. It isn't pretty, but it includes the basic overview and some " +"discussion\n" +"that ensued." +msgstr "" + +#: i2p2www/pages/site/misc/myi2p.html:12 +#, python-format +msgid "" +"The application itself is not yet implemented, and the ideas behind it " +"have \n" +"been made less ambitious over time, but they are still valid and the " +"current \n" +"plan is to have the core MyI2P functionality " +"available \n" +"along side the I2P 1.0 release. That will include a distributed address " +"book\n" +"to enable secure, distributed, and human readable naming by sacrificing " +"the \n" +"need for global uniqueness - basically everyone has their own local " +"address book \n" +"and can 'subscribe' to other people's address books, letting MyI2P " +"periodically\n" +"retrieve new name to destination mappings (leaving conflicts up to the " +"user to\n" +"resolve). In addition to the address book, there will be a distributed " +"blogging\n" +"system using a reduced and secured subset of \n" +"bbcode to " +"essentially\n" +"provide an anonymous LiveJournal with\n" +"a 'friends list' and transparent access control (authenticated by the I2P" +"\n" +"datagrams with rules defined based on the " +"address book)." +msgstr "" + +#: i2p2www/pages/site/misc/myi2p.html:29 +msgid "" +"Additional functionality, such as integration with a DHT backing store or" +" \n" +"swarming file transfers for 'attachments' can be added later. Email may " +"or may\n" +"not get in the first pass either, though its implementation is " +"essentially just\n" +"a blog entry with private access, so perhaps some UI designer can come up" +" with\n" +"something. Exporting the data to RSS or access through ATOM will be an " +"option \n" +"down the road as well." +msgstr "" + +#: i2p2www/pages/site/misc/ratestats.html:2 +#: i2p2www/pages/site/misc/ratestats.html:5 +msgid "RateStat list" +msgstr "" + +#: i2p2www/pages/site/misc/ratestats.html:6 +msgid "I2P enables the collection of a wide range of rates." +msgstr "" + +#: i2p2www/pages/site/misc/ratestats.html:7 +msgid "" +"The list was gathered using the following command in the top directory of" +" the branch i2p.i2p:" +msgstr "" + +#: i2p2www/pages/site/misc/ratestats.html:10 +msgid "All options aren't needed, but it works." +msgstr "" + +#: i2p2www/pages/site/misc/transition-guide.html:4 +#, python-format +msgid "" +"The I2P sourcecode is kept in several distributed monotone repositories.\n" +"See the\n" +"Monotone website for information\n" +"on monotone.\n" +"See\n" +"this forum post on i2p " +"monotone\n" +"for more information on how to get started and check out the source " +"anonymously.\n" +"There is also a quick-start guide on the\n" +"new developer's page." +msgstr "" + +#: i2p2www/pages/site/misc/transition-guide.html:16 +msgid "" +"If you want to get the source non-anonymously, pull from the public " +"server mtn.welterde.de.\n" +"The i2p source code branch is \"i2p.i2p\"." +msgstr "" +"Se deseja obter o fonte de maneira não-anônima, puxe-o do servidor " +"público mtn.welterde.de.\n" +"O ramo do código-fonte é \"i2p.i2p\"." + +#: i2p2www/pages/site/misc/transition-guide.html:21 +msgid "Guide" +msgstr "Guia" + +#: i2p2www/pages/site/misc/transition-guide.html:22 +msgid "" +"\n" +"The following is a detailed guide by Complication." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:2 +msgid "How to Upgrade from 0.6.1.30 and Earlier" +msgstr "Como atualizar a partir da versão 0.6.1.30 e anteriores" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:6 +msgid "Upgrading from 0.6.1.30 and Earlier Releases" +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:8 +#, python-format +msgid "" +"Since i2p's lead developer\n" +"has gone AWOL,\n" +"we do not have his update signing key or access to\n" +"www.i2p[.net] or dev.i2p[.net].\n" +"Complication and zzz have generated new signing keys, and they and Amiga " +"are providing\n" +"update file hosting. These changes must be configured in your router to " +"take effect." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:17 +msgid "" +"Make the following configuration changes and your router will " +"automatically install\n" +"the latest release." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:22 +#, python-format +msgid "" +"We recommend the automated process as it will verify the key of the " +"signed update file.\n" +"If you do not make these changes,\n" +"you may manually download the i2pupdate.zip file from\n" +"the download page." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:34 +#, python-format +msgid "Change the News URL to: %(url)s" +msgstr "Mude o URL de notícias para: %(url)s" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:38 +msgid "" +"Select ONE of the following new Update URLs at random and enter it into " +"the Update URL box: " +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:43 +msgid "Check the box \"Update through the eepProxy?\"" +msgstr "Selecionar a opção \"Atualizar através de eepProxy?\"" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44 +msgid "Click \"Save\"" +msgstr "Clique em \"Salvar\"" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51 +msgid "Add the following line:" +msgstr "Adicione a seguinte linha:" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55 +msgid "Click \"Apply\"" +msgstr "Clique em \"Aplicar\"" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:58 +msgid "" +"You are now ready to automatically receive the release update file,\n" +"either by setting your update policy to \"download and install\" or by " +"clicking on the\n" +"\"update available\" link when it appears." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:65 +#, python-format +msgid "" +"If you would like to verify the trusted update keys, they are also\n" +"posted and signed here.\n" +"Thank you for your support during this transition. For help please " +"contact us on #i2p." +msgstr "" + diff --git a/i2p2www/translations/zh_CN/LC_MESSAGES/about.po b/i2p2www/translations/zh_CN/LC_MESSAGES/about.po new file mode 100644 index 00000000..1a242f1a --- /dev/null +++ b/i2p2www/translations/zh_CN/LC_MESSAGES/about.po @@ -0,0 +1,2193 @@ +# Chinese (China) translations for I2P. +# Copyright (C) 2013 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# kwh <14alpaca@gmail.com>, 2013 +# Y.F Yang , 2014 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2013-12-30 05:56+0000\n" +"PO-Revision-Date: 2014-01-04 14:33+0000\n" +"Last-Translator: Y.F Yang \n" +"Language-Team: Chinese (China) " +"(http://www.transifex.com/projects/p/I2P/language/zh_CN/)\n" +"Plural-Forms: nplurals=1; plural=0\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 0.9.6\n" + +#: i2p2www/pages/site/about/browser-config.html:2 +msgid "Web Browser Configuration" +msgstr "网页浏览器配置" + +#: i2p2www/pages/site/about/browser-config.html:5 +msgid "" +"Your web browser will need to be configured in order to browse eepsites " +"and to\n" +"utilize the outproxies available within I2P. Below are walkthroughs for " +"some of\n" +"the most popular browsers." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:11 +msgid "How to configure your browser" +msgstr "如何设置您的浏览器" + +#: i2p2www/pages/site/about/browser-config.html:17 +#: i2p2www/pages/site/about/browser-config.html:73 +msgid "Outproxy Terms Of Service" +msgstr "出口代理使用协议" + +#: i2p2www/pages/site/about/browser-config.html:22 +msgid "Internet Explorer 8 or Chrome" +msgstr "IE8或Chrome浏览器" + +#: i2p2www/pages/site/about/browser-config.html:23 +msgid "" +"In the tools menu select the \"Internet Options\" line to open the " +"settings. In the\n" +"settings window choose the connections tab and click on LAN settings for " +"the\n" +"proxy port configuration." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:28 +msgid "IE Internet Options" +msgstr "IE Internet选项" + +#: i2p2www/pages/site/about/browser-config.html:29 +msgid "" +"Now set the checkmark at \"use a proxy server for your LAN\" and at the " +"\"Bypass\n" +"proxy server for local addresses\". With a click on Advanced-button you " +"open the\n" +"window to open the ports. Enter the values like on the picture, IP " +"127.0.0.1\n" +"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save " +"the\n" +"settings and your browser is set to use the I2P proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:36 +msgid "IE Proxy Settings" +msgstr "IE 代理设置" + +#: i2p2www/pages/site/about/browser-config.html:40 +msgid "" +"From the Tools menu, select Options to bring up the Firefox settings " +"panel.\n" +"Click the icon labelled Advanced, then click on the " +"Network\n" +"tab. In the Connections section, click on the Settings button. " +"You'll\n" +"see a Window like the following:" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:46 +msgid "Firefox Network Options" +msgstr "Firefox 网络选项" + +#: i2p2www/pages/site/about/browser-config.html:47 +msgid "" +"In the Connection Settings window, click the circle next to " +"Manual\n" +" proxy configuration, then enter 127.0.0.1, port 4444 in the HTTP" +" Proxy\n" +"field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.\n" +"Be sure to enter localhost and 127.0.0.1 into the \"No Proxy for\" box." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:53 +msgid "Firefox Proxy Settings" +msgstr "Firefox 代理设置" + +#: i2p2www/pages/site/about/browser-config.html:57 +msgid "" +"From the Settings menu, select Configure Konqueror. In " +"the\n" +"Web Browsing group on the left side, select Proxy Services.\n" +"In this new window, select the option \"Manually specify the proxy " +"settings\" and\n" +"click the Setup box." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:63 +msgid "Konqueror Proxy Options" +msgstr "Konqueror 代理选项" + +#: i2p2www/pages/site/about/browser-config.html:64 +msgid "" +"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port" +" 4445 into\n" +"HTTPS box. Click the New button in the Exceptions section. Enter" +"\n" +"localhost and click OK. Click the New button once more and enter" +"\n" +"127.0.0.1 and OK. Hit OK once more to close the configuration window." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:70 +msgid "Konqueror Proxy Ports" +msgstr "Konqueror 代理端口" + +#: i2p2www/pages/site/about/browser-config.html:74 +msgid "" +"Remember: I2P was not designed for creating proxies to the outer " +"Internet.\n" +"Instead, it is meant to be used as an internal network." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:78 +msgid "" +"The I2P project itself does not run any proxies to the Internet. Any " +"such proxy\n" +"services are run by by private volunteers and could be shut down or\n" +"unreachable at anytime." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:83 +#, python-format +msgid "" +"By default, I2P comes with two outproxies configured: " +"%(http)s\n" +"(an HTTP-only proxy) and %(https)s (an HTTPS proxy\n" +"routed through Tor." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:88 +msgid "" +"Both of these outproxies are configured with connection limits. This " +"means\n" +"that only set amount of accesses are allowed per client. Once the limit " +"is\n" +"reached, the client is blocked out for a timeframe of 1min/1h/1 day. Be\n" +"respectful and do not overload these services with too many requests!" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:94 +msgid "" +"Filtering is active on these outproxies (for example, mibbit and torrent\n" +"tracker access is blocked). Eepsites\n" +"that are accessible via .i2p addresses are also not allowed via the " +"outproxies.\n" +"As a convenience, false.i2p blocks ad servers." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:100 +msgid "" +"Tor is good application to use" +" as an\n" +"outproxy to the Internet." +msgstr "" + +#: i2p2www/pages/site/about/glossary.html:2 +msgid "Glossary" +msgstr "词汇表" + +#: i2p2www/pages/site/about/glossary.html:4 +msgid "" +"This page lists often-used terminology when discussing I2P and " +"cryptography." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:2 +msgid "Hall Of Fame" +msgstr "名人堂" + +#: i2p2www/pages/site/about/hall-of-fame.html:5 +msgid "I2P's Hall of Fame" +msgstr "I2P 名人堂" + +#: i2p2www/pages/site/about/hall-of-fame.html:6 +#, python-format +msgid "Current balance: as of %(date)s" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:9 +#: i2p2www/pages/site/about/hall-of-fame.html:47 +#: i2p2www/pages/site/about/hall-of-fame.html:173 +#: i2p2www/pages/site/about/hall-of-fame.html:174 +#: i2p2www/pages/site/about/hall-of-fame.html:175 +#: i2p2www/pages/site/about/hall-of-fame.html:176 +#: i2p2www/pages/site/about/hall-of-fame.html:178 +#: i2p2www/pages/site/about/hall-of-fame.html:179 +#: i2p2www/pages/site/about/hall-of-fame.html:180 +#: i2p2www/pages/site/about/hall-of-fame.html:183 +#: i2p2www/pages/site/about/hall-of-fame.html:184 +#: i2p2www/pages/site/about/hall-of-fame.html:185 +#: i2p2www/pages/site/about/hall-of-fame.html:188 +#: i2p2www/pages/site/about/hall-of-fame.html:189 +#: i2p2www/pages/site/about/hall-of-fame.html:190 +#: i2p2www/pages/site/about/hall-of-fame.html:191 +#: i2p2www/pages/site/about/hall-of-fame.html:192 +#: i2p2www/pages/site/about/hall-of-fame.html:193 +#: i2p2www/pages/site/about/hall-of-fame.html:194 +#: i2p2www/pages/site/about/hall-of-fame.html:195 +#: i2p2www/pages/site/about/hall-of-fame.html:196 +#: i2p2www/pages/site/about/hall-of-fame.html:197 +#: i2p2www/pages/site/about/hall-of-fame.html:198 +#: i2p2www/pages/site/about/hall-of-fame.html:199 +#: i2p2www/pages/site/about/hall-of-fame.html:200 +#: i2p2www/pages/site/about/hall-of-fame.html:203 +#: i2p2www/pages/site/about/hall-of-fame.html:204 +#: i2p2www/pages/site/about/hall-of-fame.html:205 +#: i2p2www/pages/site/about/hall-of-fame.html:206 +#: i2p2www/pages/site/about/hall-of-fame.html:207 +#: i2p2www/pages/site/about/hall-of-fame.html:208 +#: i2p2www/pages/site/about/hall-of-fame.html:210 +#: i2p2www/pages/site/about/hall-of-fame.html:211 +#: i2p2www/pages/site/about/hall-of-fame.html:214 +#: i2p2www/pages/site/about/hall-of-fame.html:215 +#: i2p2www/pages/site/about/hall-of-fame.html:216 +#: i2p2www/pages/site/about/hall-of-fame.html:217 +#: i2p2www/pages/site/about/hall-of-fame.html:218 +#: i2p2www/pages/site/about/hall-of-fame.html:220 +#: i2p2www/pages/site/about/hall-of-fame.html:221 +#: i2p2www/pages/site/about/hall-of-fame.html:222 +#: i2p2www/pages/site/about/hall-of-fame.html:223 +#: i2p2www/pages/site/about/hall-of-fame.html:224 +#: i2p2www/pages/site/about/hall-of-fame.html:225 +#: i2p2www/pages/site/about/hall-of-fame.html:227 +#: i2p2www/pages/site/about/hall-of-fame.html:228 +#: i2p2www/pages/site/about/hall-of-fame.html:229 +#: i2p2www/pages/site/about/hall-of-fame.html:230 +#: i2p2www/pages/site/about/hall-of-fame.html:232 +#: i2p2www/pages/site/about/hall-of-fame.html:233 +#: i2p2www/pages/site/about/hall-of-fame.html:234 +#: i2p2www/pages/site/about/hall-of-fame.html:235 +#: i2p2www/pages/site/about/hall-of-fame.html:236 +#: i2p2www/pages/site/about/hall-of-fame.html:239 +#: i2p2www/pages/site/about/hall-of-fame.html:240 +#: i2p2www/pages/site/about/hall-of-fame.html:241 +#: i2p2www/pages/site/about/hall-of-fame.html:242 +#: i2p2www/pages/site/about/hall-of-fame.html:244 +#: i2p2www/pages/site/about/hall-of-fame.html:245 +#: i2p2www/pages/site/about/hall-of-fame.html:246 +#: i2p2www/pages/site/about/hall-of-fame.html:248 +#: i2p2www/pages/site/about/hall-of-fame.html:249 +#: i2p2www/pages/site/about/hall-of-fame.html:250 +#: i2p2www/pages/site/about/hall-of-fame.html:251 +#: i2p2www/pages/site/about/hall-of-fame.html:253 +#: i2p2www/pages/site/about/hall-of-fame.html:254 +#: i2p2www/pages/site/about/hall-of-fame.html:255 +#: i2p2www/pages/site/about/hall-of-fame.html:256 +#: i2p2www/pages/site/about/hall-of-fame.html:257 +#: i2p2www/pages/site/about/hall-of-fame.html:263 +#: i2p2www/pages/site/about/hall-of-fame.html:266 +#: i2p2www/pages/site/about/hall-of-fame.html:267 +#: i2p2www/pages/site/about/hall-of-fame.html:268 +#: i2p2www/pages/site/about/hall-of-fame.html:269 +#: i2p2www/pages/site/about/hall-of-fame.html:270 +#: i2p2www/pages/site/about/hall-of-fame.html:272 +#: i2p2www/pages/site/about/hall-of-fame.html:273 +#: i2p2www/pages/site/about/hall-of-fame.html:274 +#: i2p2www/pages/site/about/hall-of-fame.html:279 +#: i2p2www/pages/site/about/hall-of-fame.html:280 +#: i2p2www/pages/site/about/hall-of-fame.html:281 +#: i2p2www/pages/site/about/hall-of-fame.html:282 +#: i2p2www/pages/site/about/hall-of-fame.html:283 +#: i2p2www/pages/site/about/hall-of-fame.html:284 +#: i2p2www/pages/site/about/hall-of-fame.html:285 +#: i2p2www/pages/site/about/hall-of-fame.html:286 +#: i2p2www/pages/site/about/hall-of-fame.html:287 +#: i2p2www/pages/site/about/hall-of-fame.html:288 +#: i2p2www/pages/site/about/hall-of-fame.html:290 +#: i2p2www/pages/site/about/hall-of-fame.html:291 +#: i2p2www/pages/site/about/hall-of-fame.html:301 +#: i2p2www/pages/site/about/hall-of-fame.html:302 +#: i2p2www/pages/site/about/hall-of-fame.html:303 +#: i2p2www/pages/site/about/hall-of-fame.html:304 +#: i2p2www/pages/site/about/hall-of-fame.html:305 +#: i2p2www/pages/site/about/hall-of-fame.html:306 +#: i2p2www/pages/site/about/hall-of-fame.html:307 +#: i2p2www/pages/site/about/hall-of-fame.html:308 +#: i2p2www/pages/site/about/hall-of-fame.html:309 +#: i2p2www/pages/site/about/hall-of-fame.html:310 +#: i2p2www/pages/site/about/hall-of-fame.html:311 +#: i2p2www/pages/site/about/hall-of-fame.html:312 +#: i2p2www/pages/site/about/hall-of-fame.html:313 +#: i2p2www/pages/site/about/hall-of-fame.html:314 +#: i2p2www/pages/site/about/hall-of-fame.html:315 +#: i2p2www/pages/site/about/hall-of-fame.html:316 +#: i2p2www/pages/site/about/hall-of-fame.html:317 +#: i2p2www/pages/site/about/hall-of-fame.html:318 +#: i2p2www/pages/site/about/hall-of-fame.html:319 +#: i2p2www/pages/site/about/hall-of-fame.html:320 +#: i2p2www/pages/site/about/hall-of-fame.html:321 +#: i2p2www/pages/site/about/hall-of-fame.html:325 +#: i2p2www/pages/site/about/hall-of-fame.html:326 +#: i2p2www/pages/site/about/hall-of-fame.html:327 +#: i2p2www/pages/site/about/hall-of-fame.html:328 +#: i2p2www/pages/site/about/hall-of-fame.html:329 +#: i2p2www/pages/site/about/hall-of-fame.html:330 +#: i2p2www/pages/site/about/hall-of-fame.html:331 +#: i2p2www/pages/site/about/hall-of-fame.html:333 +#: i2p2www/pages/site/about/hall-of-fame.html:334 +#: i2p2www/pages/site/about/hall-of-fame.html:335 +#: i2p2www/pages/site/about/hall-of-fame.html:336 +#: i2p2www/pages/site/about/hall-of-fame.html:337 +#: i2p2www/pages/site/about/hall-of-fame.html:338 +#: i2p2www/pages/site/about/hall-of-fame.html:339 +#: i2p2www/pages/site/about/hall-of-fame.html:340 +#: i2p2www/pages/site/about/hall-of-fame.html:341 +#: i2p2www/pages/site/about/hall-of-fame.html:344 +#: i2p2www/pages/site/about/hall-of-fame.html:345 +#: i2p2www/pages/site/about/hall-of-fame.html:346 +#: i2p2www/pages/site/about/hall-of-fame.html:347 +#: i2p2www/pages/site/about/hall-of-fame.html:348 +#: i2p2www/pages/site/about/hall-of-fame.html:350 +#: i2p2www/pages/site/about/hall-of-fame.html:352 +#: i2p2www/pages/site/about/hall-of-fame.html:353 +#: i2p2www/pages/site/about/hall-of-fame.html:354 +#: i2p2www/pages/site/about/hall-of-fame.html:355 +#: i2p2www/pages/site/about/hall-of-fame.html:356 +#: i2p2www/pages/site/about/hall-of-fame.html:357 +#: i2p2www/pages/site/about/hall-of-fame.html:358 +#: i2p2www/pages/site/about/hall-of-fame.html:360 +#: i2p2www/pages/site/about/hall-of-fame.html:361 +#: i2p2www/pages/site/about/hall-of-fame.html:362 +#: i2p2www/pages/site/about/hall-of-fame.html:363 +#: i2p2www/pages/site/about/hall-of-fame.html:364 +#: i2p2www/pages/site/about/hall-of-fame.html:365 +#: i2p2www/pages/site/about/hall-of-fame.html:366 +#: i2p2www/pages/site/about/hall-of-fame.html:367 +#: i2p2www/pages/site/about/hall-of-fame.html:368 +#: i2p2www/pages/site/about/hall-of-fame.html:369 +#: i2p2www/pages/site/about/hall-of-fame.html:370 +#: i2p2www/pages/site/about/hall-of-fame.html:371 +#: i2p2www/pages/site/about/hall-of-fame.html:372 +#: i2p2www/pages/site/about/hall-of-fame.html:373 +#: i2p2www/pages/site/about/hall-of-fame.html:375 +#: i2p2www/pages/site/about/hall-of-fame.html:376 +#: i2p2www/pages/site/about/hall-of-fame.html:377 +#: i2p2www/pages/site/about/hall-of-fame.html:380 +#: i2p2www/pages/site/about/hall-of-fame.html:381 +#: i2p2www/pages/site/about/hall-of-fame.html:384 +#: i2p2www/pages/site/about/hall-of-fame.html:385 +#: i2p2www/pages/site/about/hall-of-fame.html:387 +#: i2p2www/pages/site/about/hall-of-fame.html:388 +#: i2p2www/pages/site/about/hall-of-fame.html:401 +#: i2p2www/pages/site/about/hall-of-fame.html:402 +#: i2p2www/pages/site/about/hall-of-fame.html:403 +#: i2p2www/pages/site/about/hall-of-fame.html:404 +#: i2p2www/pages/site/about/hall-of-fame.html:405 +#: i2p2www/pages/site/about/hall-of-fame.html:406 +#: i2p2www/pages/site/about/hall-of-fame.html:407 +#: i2p2www/pages/site/about/hall-of-fame.html:408 +#: i2p2www/pages/site/about/hall-of-fame.html:409 +#: i2p2www/pages/site/about/hall-of-fame.html:410 +#: i2p2www/pages/site/about/hall-of-fame.html:411 +#: i2p2www/pages/site/about/hall-of-fame.html:412 +#: i2p2www/pages/site/about/hall-of-fame.html:413 +#: i2p2www/pages/site/about/hall-of-fame.html:414 +#: i2p2www/pages/site/about/hall-of-fame.html:415 +#: i2p2www/pages/site/about/hall-of-fame.html:416 +#: i2p2www/pages/site/about/hall-of-fame.html:417 +#: i2p2www/pages/site/about/hall-of-fame.html:418 +#: i2p2www/pages/site/about/hall-of-fame.html:419 +#: i2p2www/pages/site/about/hall-of-fame.html:420 +#: i2p2www/pages/site/about/hall-of-fame.html:421 +#: i2p2www/pages/site/about/hall-of-fame.html:422 +#: i2p2www/pages/site/about/hall-of-fame.html:423 +#: i2p2www/pages/site/about/hall-of-fame.html:424 +#: i2p2www/pages/site/about/hall-of-fame.html:425 +#: i2p2www/pages/site/about/hall-of-fame.html:426 +#: i2p2www/pages/site/about/hall-of-fame.html:427 +#: i2p2www/pages/site/about/hall-of-fame.html:428 +#: i2p2www/pages/site/about/hall-of-fame.html:429 +#: i2p2www/pages/site/about/hall-of-fame.html:430 +#: i2p2www/pages/site/about/hall-of-fame.html:431 +#: i2p2www/pages/site/about/hall-of-fame.html:432 +#: i2p2www/pages/site/about/hall-of-fame.html:433 +#: i2p2www/pages/site/about/hall-of-fame.html:434 +#: i2p2www/pages/site/about/hall-of-fame.html:435 +#: i2p2www/pages/site/about/hall-of-fame.html:437 +#: i2p2www/pages/site/about/hall-of-fame.html:438 +#: i2p2www/pages/site/about/hall-of-fame.html:439 +#: i2p2www/pages/site/about/hall-of-fame.html:440 +#: i2p2www/pages/site/about/hall-of-fame.html:441 +#: i2p2www/pages/site/about/hall-of-fame.html:442 +#: i2p2www/pages/site/about/hall-of-fame.html:443 +#: i2p2www/pages/site/about/hall-of-fame.html:444 +#: i2p2www/pages/site/about/hall-of-fame.html:446 +#: i2p2www/pages/site/about/hall-of-fame.html:447 +#: i2p2www/pages/site/about/hall-of-fame.html:448 +#: i2p2www/pages/site/about/hall-of-fame.html:450 +#: i2p2www/pages/site/about/hall-of-fame.html:451 +#: i2p2www/pages/site/about/hall-of-fame.html:452 +#: i2p2www/pages/site/about/hall-of-fame.html:453 +#: i2p2www/pages/site/about/hall-of-fame.html:454 +#: i2p2www/pages/site/about/hall-of-fame.html:456 +#: i2p2www/pages/site/about/hall-of-fame.html:459 +#: i2p2www/pages/site/about/hall-of-fame.html:460 +#: i2p2www/pages/site/about/hall-of-fame.html:461 +#: i2p2www/pages/site/about/hall-of-fame.html:462 +#: i2p2www/pages/site/about/hall-of-fame.html:463 +#: i2p2www/pages/site/about/hall-of-fame.html:464 +#: i2p2www/pages/site/about/hall-of-fame.html:465 +#: i2p2www/pages/site/about/hall-of-fame.html:466 +#: i2p2www/pages/site/about/hall-of-fame.html:467 +#: i2p2www/pages/site/about/hall-of-fame.html:468 +#: i2p2www/pages/site/about/hall-of-fame.html:469 +#: i2p2www/pages/site/about/hall-of-fame.html:470 +#: i2p2www/pages/site/about/hall-of-fame.html:471 +#: i2p2www/pages/site/about/hall-of-fame.html:472 +#: i2p2www/pages/site/about/hall-of-fame.html:474 +#: i2p2www/pages/site/about/hall-of-fame.html:475 +#: i2p2www/pages/site/about/hall-of-fame.html:476 +#: i2p2www/pages/site/about/hall-of-fame.html:478 +#: i2p2www/pages/site/about/hall-of-fame.html:481 +#: i2p2www/pages/site/about/hall-of-fame.html:482 +#: i2p2www/pages/site/about/hall-of-fame.html:483 +#: i2p2www/pages/site/about/hall-of-fame.html:484 +#: i2p2www/pages/site/about/hall-of-fame.html:485 +#: i2p2www/pages/site/about/hall-of-fame.html:486 +#: i2p2www/pages/site/about/hall-of-fame.html:487 +#: i2p2www/pages/site/about/hall-of-fame.html:488 +#: i2p2www/pages/site/about/hall-of-fame.html:489 +#: i2p2www/pages/site/about/hall-of-fame.html:490 +#: i2p2www/pages/site/about/hall-of-fame.html:491 +#: i2p2www/pages/site/about/hall-of-fame.html:492 +#: i2p2www/pages/site/about/hall-of-fame.html:493 +#: i2p2www/pages/site/about/hall-of-fame.html:494 +#: i2p2www/pages/site/about/hall-of-fame.html:495 +#: i2p2www/pages/site/about/hall-of-fame.html:496 +#: i2p2www/pages/site/about/hall-of-fame.html:497 +#: i2p2www/pages/site/about/hall-of-fame.html:498 +#: i2p2www/pages/site/about/hall-of-fame.html:499 +#: i2p2www/pages/site/about/hall-of-fame.html:501 +#: i2p2www/pages/site/about/hall-of-fame.html:502 +#: i2p2www/pages/site/about/hall-of-fame.html:503 +msgid "General fund" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:10 +#: i2p2www/pages/site/about/hall-of-fame.html:12 +#: i2p2www/pages/site/about/hall-of-fame.html:14 +#: i2p2www/pages/site/about/hall-of-fame.html:20 +#, python-format +msgid "%(euroval)s € and %(btcval)s BTC" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:11 +msgid "Datastorage bounty" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:13 +msgid "Native IPv6 I2P" +msgstr "原生 IPv6 I2P" + +#: i2p2www/pages/site/about/hall-of-fame.html:15 +msgid "I2PHex bounty" +msgstr "I2PHex 赏金" + +#: i2p2www/pages/site/about/hall-of-fame.html:16 +#: i2p2www/pages/site/about/hall-of-fame.html:18 +#: i2p2www/pages/site/about/hall-of-fame.html:22 +#, python-format +msgid "%(euroval)s €" +msgstr "%(euroval)s €" + +#: i2p2www/pages/site/about/hall-of-fame.html:17 +msgid "I2P in debian mirrors" +msgstr "I2P 在 debian 镜像" + +#: i2p2www/pages/site/about/hall-of-fame.html:19 +msgid "Bitcoin client for I2P" +msgstr "I2P 的比特币客户端" + +#: i2p2www/pages/site/about/hall-of-fame.html:21 +msgid "Unit Tests for I2P router" +msgstr "I2P 路由的单元测试" + +#: i2p2www/pages/site/about/hall-of-fame.html:23 +msgid "Bounty Robert" +msgstr "罗伯特赏金" + +#: i2p2www/pages/site/about/hall-of-fame.html:24 +msgid "Bounty Syndie" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:25 +msgid "Bounty I2P for CCR Microtic Board" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:28 +msgid "Current monthly running costs:" +msgstr "目前每月运行费用：" + +#: i2p2www/pages/site/about/hall-of-fame.html:39 +msgid "Big thanks go to the following people who have donated to I2P!" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:40 +#, python-format +msgid "" +"If you have made a donation, please send an email to echelon\n" +"with your name or nick (and optionally homepage) so we can list you here." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:45 +msgid "Current monthly subscriptions:" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:51 +msgid "2013 donations and costs:" +msgstr "2013年的捐赠与花费：" + +#: i2p2www/pages/site/about/hall-of-fame.html:170 +msgid "2012 donations and costs:" +msgstr "2012年的捐赠与花费：" + +#: i2p2www/pages/site/about/hall-of-fame.html:298 +msgid "2011 donations and costs:" +msgstr "2011年的捐赠与花费：" + +#: i2p2www/pages/site/about/hall-of-fame.html:399 +msgid "Previous to 2011 donations:" +msgstr "2011年以前的捐赠：" + +#: i2p2www/pages/site/about/intro.html:2 +msgid "Intro" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:4 +msgid "The Invisible Internet Project" +msgstr "隐形互联网项目" + +#: i2p2www/pages/site/about/intro.html:5 +#, python-format +msgid "" +"I2P is an anonymous network, exposing a simple layer that applications " +"can \n" +"use to anonymously and securely send messages to each other. The network " +"itself is \n" +"strictly message based (a la IP), but there is a \n" +"library available to allow reliable streaming communication on top of it " +"(a la \n" +"TCP). \n" +"All communication is end to end encrypted (in total there are four layers" +" of \n" +"encryption used when sending a message), and even the end points " +"(\"destinations\") \n" +"are cryptographic identifiers (essentially a pair of public keys)." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:18 +msgid "How does it work?" +msgstr "如何运作？" + +#: i2p2www/pages/site/about/intro.html:20 +#, python-format +msgid "" +"To anonymize the messages sent, each client application has their I2P " +"\"router\"\n" +"build a few inbound and outbound \"tunnels\" - a \n" +"sequence of peers that pass messages in one direction (to and from the " +"client, \n" +"respectively). In turn, when a client wants to send a message to another" +" client, \n" +"the client passes that message out one of their outbound tunnels " +"targeting one of the \n" +"other client's inbound tunnels, eventually reaching the destination. " +"Every \n" +"participant in the network chooses the length of these tunnels, and in " +"doing so, \n" +"makes a tradeoff between anonymity, latency, and throughput according to " +"their \n" +"own needs. The result is that the number of peers relaying each end to " +"end \n" +"message is the absolute minimum necessary to meet both the sender's and " +"the \n" +"receiver's threat model." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:34 +#, python-format +msgid "" +"The first time a client wants to contact another client, they make a " +"query \n" +"against the fully distributed \"network \n" +"database\" - a custom structured \n" +"distributed hash table (DHT) based off the \n" +"Kademlia algorithm. This is done \n" +"to find the other client's inbound tunnels efficiently, but subsequent " +"messages \n" +"between them usually includes that data so no further network database " +"lookups \n" +"are required." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:47 +#, python-format +msgid "More details about how I2P works are available." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:51 +msgid "What can you do with it?" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:53 +#, python-format +msgid "" +"Within the I2P network, applications are not restricted in how they can \n" +"communicate - those that typically use UDP can make use of the base I2P \n" +"functionality, and those that typically use TCP can use the TCP-like " +"streaming\n" +"library. We have a generic TCP/I2P bridge application \n" +"(\"I2PTunnel\") that enables people to " +"forward TCP streams\n" +"into the I2P network as well as to receive streams out of the network and" +" \n" +"forward them towards a specific TCP/IP address." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:63 +#, python-format +msgid "" +"I2PTunnel is currently used to let people run their own anonymous website" +" \n" +"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel " +"'server' \n" +"at it, which people can access anonymously over I2P with a normal web " +"browser \n" +"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use " +"the same \n" +"technique to run an anonymous IRC network (where the IRC server is hosted" +" \n" +"anonymously, and standard IRC clients use an I2PTunnel to contact it). " +"There \n" +"are other application development efforts going on as well, such as one " +"to \n" +"build an optimized swarming file transfer application (a la \n" +"BitTorrent), a \n" +"distributed data store (a la Freenet / \n" +"MNet), and a blogging system (a fully \n" +"distributed LiveJournal), but those are \n" +"not ready for use yet." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:82 +#, python-format +msgid "" +"I2P is not inherently an \"outproxy\" network - the client you send a " +"message \n" +"to is the cryptographic identifier, not some IP address, so the message " +"must \n" +"be addressed to someone running I2P. However, it is possible for that " +"client\n" +"to be an outproxy, allowing you to anonymously make use of their Internet" +" \n" +"connection. To demonstrate this, the \"eepproxy\" will accept normal " +"non-I2P \n" +"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific " +"destination\n" +"that runs a squid HTTP proxy, allowing \n" +"simple anonymous browsing of the normal web. Simple outproxies like that" +" are \n" +"not viable in the long run for several reasons (including the cost of " +"running \n" +"one as well as the anonymity and security issues they introduce), but in" +" \n" +"certain circumstances the technique could be appropriate." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:96 +#, python-format +msgid "" +"The I2P development team is an open group, " +"welcome to all \n" +"who are interested in getting involved, and" +" all of \n" +"the code is open source. The core I2P SDK " +"and the \n" +"current router implementation is done in Java (currently working with " +"both \n" +"sun and kaffe, gcj support planned for later), and there is a \n" +"simple socket based API for accessing the network" +" from \n" +"other languages (with a C library available, and both Python and Perl in" +" \n" +"development). The network is actively being developed and has not yet " +"reached \n" +"the 1.0 release, but the current roadmap " +"describes \n" +"our schedule." +msgstr "" + +#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4 +msgid "Presentations on I2P" +msgstr "" + +#: i2p2www/pages/site/about/media.html:5 +#, python-format +msgid "" +"Following are links to presentations, videos, and tutorials about I2P. " +"Links to research papers on I2P are available here." +msgstr "" + +#: i2p2www/pages/site/about/media.html:8 +#, python-format +msgid "To request an addition to this page, please send to %(email)s." +msgstr "" + +#: i2p2www/pages/site/about/media.html:11 +msgid "" +"\n" +"Newest links are at the bottom of each section." +msgstr "" + +#: i2p2www/pages/site/about/media.html:16 +msgid "Presentations" +msgstr "" + +#: i2p2www/pages/site/about/media.html:19 +#, python-format +msgid "" +"IIP Presentation at CodeCon\n" +"MP3 audio\n" +"transcript\n" +"Lance James (0x90), February 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:27 +#, python-format +msgid "" +"IIP Presentation at ToorCon\n" +"MP3 audio\n" +"slides\n" +"Lance James (0x90), September 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:35 +#, python-format +msgid "" +"To Be or I2P\n" +"(Youtube Video)\n" +"An introduction into anonymous communication with I2P.\n" +"To Be or I2P (PDF presentation),\n" +"Jens Kubieziel, 24C3 Berlin, December 28, 2007." +msgstr "" + +#: i2p2www/pages/site/about/media.html:44 +#, python-format +msgid "" +"Video of I2P talk at Chemnitz Linux Tag,\n" +"Lars Schimmer,\n" +"March 14-15, 2009" +msgstr "" + +#: i2p2www/pages/site/about/media.html:50 +#, python-format +msgid "" +"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of" +" Adrian Hong's talk\n" +"\"Hackers for Human Rights\".\n" +"MP3 audio" +msgstr "" + +#: i2p2www/pages/site/about/media.html:56 +#, python-format +msgid "" +"Into the I2P Darknet: Welcome to Cipherspace\n" +"Adrian Crenshaw. Schmoocon Firetalk, January 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:61 +#, python-format +msgid "" +"Using techhnology to advance liberty\n" +"(Youtube Video)\n" +"Eric Johnson.\n" +"Agora I/O Unconference, March 27," +" 2011.\n" +"I2P covered from 10:00 to 20:00 in the video." +msgstr "" + +#: i2p2www/pages/site/about/media.html:69 +#, python-format +msgid "" +"The Bright side of darknets, FOSSCOMM Patras May " +"2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:73 +#, python-format +msgid "" +"Common Darknet Weaknesses\n" +"(Youtube Video)\n" +"Adrian Crenshaw, AIDE, July " +"11-15, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:79 +#, python-format +msgid "" +"I2P / Tor Workshop Notes\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:84 +#, python-format +msgid "" +"Cipherspaces/Darknets: An Overview Of Attack " +"Strategies -\n" +"DEF CON Live version (Youtube Video),\n" +"\"Studio\" version (Youtube Video),\n" +"Slides (ppt)\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:94 +msgid "" +"Modern cipherspace ecosystems, 0x375 " +"0x06 4/11/2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:100 +msgid "Tutorials" +msgstr "指导教程" + +#: i2p2www/pages/site/about/media.html:103 +#, python-format +msgid "" +"I2P Windows Tutorial\n" +"(Youtube Video)\n" +"This guide will show you how to install I2P in Windows XP.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:111 +#, python-format +msgid "" +"I2P Debian Tutorial\n" +"(Youtube Video)\n" +"This will guide you through how to install I2P on a Debian Linux System.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:119 +#, python-format +msgid "" +"How to set up anonymous site in I2P\n" +"(Youtube Video)\n" +"How to set up an anonymous web site in I2P.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:126 +#, python-format +msgid "" +"I2P Tutorial Mac OS X\n" +"(Youtube Video)\n" +"A tutorial on how to run i2p on Mac OS X and how to connect to " +"irc.telecomix.i2p.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:133 +#, python-format +msgid "" +"Felix Atari explains the basic principles of I2P" +"\n" +"(Youtube Video)\n" +"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:140 +#, python-format +msgid "" +"How to get onto I2P, the anonymous P2P Darknet " +"(Windows Install)\n" +"(Youtube Video)\n" +"This tutorial shows how to install and configure software needed to " +"access I2P." +msgstr "" + +#: i2p2www/pages/site/about/media.html:146 +#, python-format +msgid "" +"How to connect to I2P\n" +"(Youtube Video)\n" +"How to install I2P on Ubuntu." +msgstr "" + +#: i2p2www/pages/site/about/media.html:152 +#, python-format +msgid "" +"Installing the I2P darknet software in Linux\n" +"(Video)\n" +"Adrian Crenshaw.\n" +"January 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:159 +#, python-format +msgid "" +"Short garlic routing animation\n" +"(Youtube Video)\n" +"Adrian Crenshaw.\n" +msgstr "" + +#: i2p2www/pages/site/about/media.html:167 +msgid "Articles and Interviews" +msgstr "文章与访谈" + +#: i2p2www/pages/site/about/media.html:170 +#, python-format +msgid "" +"0x90 Interviewed by DistributedCity\n" +"Part 1\n" +"Part 2\n" +"July 26, 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:178 +#, python-format +msgid "" +"0x90 Interviewed by El Pais\n" +"(original in Spanish)\n" +"English translation\n" +"October 31, 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:185 +#, python-format +msgid "" +"2003 Business Week article referencing " +"invisiblenet" +msgstr "" + +#: i2p2www/pages/site/about/media.html:189 +#, python-format +msgid "" +"Netzwelt.de article about being anonymous in the " +"Internet\n" +"(German)\n" +"November 2007." +msgstr "" + +#: i2p2www/pages/site/about/media.html:195 +#, python-format +msgid "" +"zzz interviewed by gulli.com\n" +"March 2009\n" +"German translation" +msgstr "" + +#: i2p2www/pages/site/about/media.html:202 +#, python-format +msgid "" +"zzz interviewed on the InfoSec Daily Podcast Ep. 454 " +"(mp3)\n" +"August 18, 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:207 +#, python-format +msgid "" +"I2P - Anonymity for the Masses,\n" +"Jonathan Cox,\n" +"November 11, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:213 +#, python-format +msgid "" +"zzz and Lance James interviewed on the InfoSec Daily " +"Podcast Ep. 596 (mp3)\n" +"February 16, 2012" +msgstr "" + +#: i2p2www/pages/site/about/team.html:2 +msgid "Team" +msgstr "团队" + +#: i2p2www/pages/site/about/team.html:4 +msgid "I2P Project Members" +msgstr "I2P 项目成员" + +#: i2p2www/pages/site/about/team.html:5 +#, python-format +msgid "" +"We are a small group of people spread around several continents, working " +"to\n" +"advance different aspects of the project and discussing the design of the" +"\n" +"network.\n" +"Get involved!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:14 +msgid "Admin" +msgstr "管理员" + +#: i2p2www/pages/site/about/team.html:15 +msgid "Project Manager" +msgstr "项目经理" + +#: i2p2www/pages/site/about/team.html:17 +msgid "point of contact of last resort" +msgstr "" + +#: i2p2www/pages/site/about/team.html:20 +msgid "Treasurer" +msgstr "财务主管" + +#: i2p2www/pages/site/about/team.html:22 +msgid "manage donations / accounts / bounties" +msgstr "" + +#: i2p2www/pages/site/about/team.html:25 +msgid "PR manager" +msgstr "公关经理" + +#: i2p2www/pages/site/about/team.html:27 +msgid "press contact, manages public relations and affairs" +msgstr "采访联系，管理公共关系和事务" + +#: i2p2www/pages/site/about/team.html:30 +#, python-format +msgid "Forum admin" +msgstr "论坛管理员" + +#: i2p2www/pages/site/about/team.html:32 +msgid "manage the public user forum" +msgstr "管理公开的用户论坛" + +#: i2p2www/pages/site/about/team.html:35 +msgid "Mirrors admin" +msgstr "镜像管理员" + +#: i2p2www/pages/site/about/team.html:37 +msgid "manage the project mirrors" +msgstr "管理项目镜像" + +#: i2p2www/pages/site/about/team.html:40 +#, python-format +msgid "Monotone guru" +msgstr "Monotone 导师" + +#: i2p2www/pages/site/about/team.html:42 +msgid "manage the public monotone repositories" +msgstr "管理公开的 monotone 版本库" + +#: i2p2www/pages/site/about/team.html:45 +msgid "Packager; Linux" +msgstr "" + +#: i2p2www/pages/site/about/team.html:47 +msgid "Linux (Debian/Ubuntu) distribution packager" +msgstr "Linux (Debian/Ubuntu) 分发包" + +#: i2p2www/pages/site/about/team.html:50 +msgid "Packager; Windows" +msgstr "" + +#: i2p2www/pages/site/about/team.html:52 +msgid "Windows installer packager" +msgstr "Windows 安装包" + +#: i2p2www/pages/site/about/team.html:55 +msgid "Release Manager" +msgstr "发布管理员" + +#: i2p2www/pages/site/about/team.html:57 +msgid "Builds and signs the releases" +msgstr "构建和签名发布版" + +#: i2p2www/pages/site/about/team.html:60 +msgid "Update admin" +msgstr "更新管理员" + +#: i2p2www/pages/site/about/team.html:62 +msgid "Monitors and recruits in-network update hosts" +msgstr "监测和吸收网内更新的主机" + +#: i2p2www/pages/site/about/team.html:65 +msgid "Reseed admin" +msgstr "补种管理" + +#: i2p2www/pages/site/about/team.html:67 +msgid "Monitors, advises and recruits reseed hosts" +msgstr "" + +#: i2p2www/pages/site/about/team.html:70 +msgid "Security expert" +msgstr "安全专家" + +#: i2p2www/pages/site/about/team.html:71 i2p2www/pages/site/about/team.html:86 +#: i2p2www/pages/site/about/team.html:91 i2p2www/pages/site/about/team.html:111 +#: i2p2www/pages/site/about/team.html:148 +#: i2p2www/pages/site/about/team.html:158 +#: i2p2www/pages/site/about/team.html:163 +#: i2p2www/pages/site/about/team.html:168 +#: i2p2www/pages/site/about/team.html:173 +#: i2p2www/pages/site/about/team.html:178 +#: i2p2www/pages/site/about/team.html:211 +msgid "vacant" +msgstr "空缺" + +#: i2p2www/pages/site/about/team.html:72 +msgid "threat model / crypto expert" +msgstr "威胁模型/加密专家" + +#: i2p2www/pages/site/about/team.html:77 +msgid "Manage the project bug tracker" +msgstr "管理项目的缺陷跟踪" + +#: i2p2www/pages/site/about/team.html:80 +msgid "Translation admins" +msgstr "翻译管理" + +#: i2p2www/pages/site/about/team.html:85 +msgid "User Advocate" +msgstr "" + +#: i2p2www/pages/site/about/team.html:87 +msgid "gather, prioritize, advocate for user needs" +msgstr "" + +#: i2p2www/pages/site/about/team.html:90 +msgid "Web Designer" +msgstr "网页设计师" + +#: i2p2www/pages/site/about/team.html:92 +msgid "manage the public project website content design" +msgstr "" + +#: i2p2www/pages/site/about/team.html:95 +#, python-format +msgid "Webserver admin" +msgstr "网站服务器管理" + +#: i2p2www/pages/site/about/team.html:97 +msgid "manage the public project webservers" +msgstr "" + +#: i2p2www/pages/site/about/team.html:100 +#, python-format +msgid "Website admin" +msgstr "网站管理" + +#: i2p2www/pages/site/about/team.html:102 +msgid "manage the public project website content" +msgstr "" + +#: i2p2www/pages/site/about/team.html:105 +msgid "News Admin" +msgstr "新闻管理" + +#: i2p2www/pages/site/about/team.html:107 +msgid "manage router console news feed" +msgstr "" + +#: i2p2www/pages/site/about/team.html:110 +msgid "Director of passion" +msgstr "" + +#: i2p2www/pages/site/about/team.html:112 +msgid "community motivator" +msgstr "" + +#: i2p2www/pages/site/about/team.html:116 +msgid "Dev" +msgstr "" + +#: i2p2www/pages/site/about/team.html:117 +msgid "Core Lead" +msgstr "核心领导者" + +#: i2p2www/pages/site/about/team.html:119 +msgid "lead dev for the SDK and router" +msgstr "牵头开发 SDK 和路由本身" + +#: i2p2www/pages/site/about/team.html:122 +#, python-format +msgid "I2P mail lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:124 +msgid "organize and develop the i2p mail system" +msgstr "" + +#: i2p2www/pages/site/about/team.html:127 +#, python-format +msgid "I2Host lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:129 +msgid "I2Host addressbook application" +msgstr "" + +#: i2p2www/pages/site/about/team.html:132 +#, python-format +msgid "BOB lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:134 +msgid "Basic Open Bridge" +msgstr "" + +#: i2p2www/pages/site/about/team.html:137 +#, python-format +msgid "I2P-Bote lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:139 +msgid "I2PBote plugin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:142 +#, python-format +msgid "Robert lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:144 +msgid "Robert BitTorrent client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:147 +#, python-format +msgid "I2Phex lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:149 +msgid "I2Phex Gnutella client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:152 +#, python-format +msgid "I2PSnark lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:154 +msgid "Maintains the integrated Bittorrent client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:157 +#, python-format +msgid "iMule lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:159 +msgid "eMule client over I2P" +msgstr "" + +#: i2p2www/pages/site/about/team.html:162 +#, python-format +msgid "Syndie lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:164 +msgid "Syndie development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:167 +msgid "Susimail lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:169 +msgid "Susimail development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:172 +msgid "Console" +msgstr "" + +#: i2p2www/pages/site/about/team.html:174 +msgid "Router console HTML/CSS design" +msgstr "" + +#: i2p2www/pages/site/about/team.html:177 +msgid "SAM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:179 +msgid "SAM maintainer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:182 +msgid "I2PCPP lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:184 +msgid "C++ Router" +msgstr "" + +#: i2p2www/pages/site/about/team.html:187 +msgid "Translators" +msgstr "翻译者" + +#: i2p2www/pages/site/about/team.html:188 +msgid "many many people!" +msgstr "许多许多人！" + +#: i2p2www/pages/site/about/team.html:193 +msgid "Contributors" +msgstr "" + +#: i2p2www/pages/site/about/team.html:195 +msgid "fire2pe dev, console enhancements" +msgstr "" + +#: i2p2www/pages/site/about/team.html:199 +msgid "desktopgui, dijjer port" +msgstr "" + +#: i2p2www/pages/site/about/team.html:203 +msgid "Debian/Ubuntu Packager and PPA maintainer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:207 +msgid "Routerconsole backend and UI work, website revamp, unit tests work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:212 +msgid "Help needed on many fronts!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:216 +msgid "Past contributors" +msgstr "" + +#: i2p2www/pages/site/about/team.html:218 +msgid "I2PTunnel development, ministreaming library" +msgstr "" + +#: i2p2www/pages/site/about/team.html:222 +msgid "Project lead, Syndie lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:226 +msgid "Project lead, Syndie lead, I2Phex, support guru" +msgstr "" + +#: i2p2www/pages/site/about/team.html:230 +msgid "iMule lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:234 +#: i2p2www/pages/site/about/team.html:238 +#: i2p2www/pages/site/about/team.html:242 +msgid "I2Phex work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:246 +msgid "Python SAM library, attack simulations" +msgstr "" + +#: i2p2www/pages/site/about/team.html:250 +msgid "i2pmail development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:254 +msgid "Syndie help" +msgstr "" + +#: i2p2www/pages/site/about/team.html:258 +msgid "i2p mail,susimail and susidns apps" +msgstr "" + +#: i2p2www/pages/site/about/team.html:262 +msgid "I2Phex (port of Phex to I2P)" +msgstr "" + +#: i2p2www/pages/site/about/team.html:266 +msgid "addressbook,i2p-bt,syndie client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:270 +msgid "organize and develop the i2p-bt BitTorrent port" +msgstr "" + +#: i2p2www/pages/site/about/team.html:274 +msgid "addressbook, i2p-bt, syndie client development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:278 +msgid "encryption and signature routines, I2PIM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:282 +msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)" +msgstr "" + +#: i2p2www/pages/site/about/team.html:286 +msgid "installer, systray, bogobot" +msgstr "" + +#: i2p2www/pages/site/about/team.html:290 +msgid "jbigi development, wiki migration, doc cleanup" +msgstr "" + +#: i2p2www/pages/site/about/team.html:294 +msgid "java debugging and client development on I2PTunnel and the router console" +msgstr "" + +#: i2p2www/pages/site/about/team.html:298 +msgid "SAM perl module" +msgstr "" + +#: i2p2www/pages/site/about/team.html:302 +msgid "i2psnark work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:306 +msgid "java cleanup" +msgstr "" + +#: i2p2www/pages/site/about/team.html:310 +msgid "docs. wiki migration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:314 +msgid "translations into French" +msgstr "" + +#: i2p2www/pages/site/about/team.html:318 +msgid "C port of jcpuid" +msgstr "" + +#: i2p2www/pages/site/about/team.html:322 +msgid "C# SAM library, pants, fortuna integration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:326 +msgid "libSAM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:330 +#: i2p2www/pages/site/about/team.html:334 +msgid "i2p-bt tracker development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:338 +msgid "Console and website themes" +msgstr "" + +#: i2p2www/pages/site/about/team.html:368 +msgid "… and many others" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:2 +msgid "Future Performance Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:4 +msgid "August 2010" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:7 +msgid "" +"There are a few major techniques that can be done to improve the " +"perceived\n" +"performance of I2P - some of the following are CPU related, others " +"bandwidth\n" +"related, and others still are protocol related. However, all of those\n" +"dimensions affect the latency, throughput, and perceived performance of " +"the\n" +"network, as they reduce contention for scarce resources. This list is of" +" course\n" +"not comprehensive, but it does cover the major ones that are seen." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:15 +#: i2p2www/pages/site/about/performance/index.html:106 +#, python-format +msgid "" +"For past performance improvements see the \n" +"Performance History." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:20 +msgid "Better peer profiling and selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:21 +#, python-format +msgid "" +"Probably one of the most important parts of getting faster performance " +"will\n" +"be improving how routers choose the peers that they build their tunnels " +"through\n" +"- making sure they don't use peers with slow links or ones with fast " +"links that\n" +"are overloaded, etc. In addition, we've got to make sure we don't expose" +"\n" +"ourselves to a Sybil attack\n" +"from a powerful adversary with lots of fast machines." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:30 +msgid "Network database tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:31 +msgid "" +"We're going to want to be more efficient with the network database's " +"healing\n" +"and maintenance algorithms - rather than constantly explore the keyspace " +"for new\n" +"peers - causing a significant number of network messages and router load " +"- we\n" +"can slow down or even stop exploring until we detect that there's " +"something new\n" +"worth finding (e.g. decay the exploration rate based upon the last time " +"someone\n" +"gave us a reference to someone we had never heard of). We can also do " +"some\n" +"tuning on what we actually send - how many peers we bounce back (or even " +"if we\n" +"bounce back a reply), as well as how many concurrent searches we perform." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:42 +msgid "Session Tag Tuning and Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:43 +#, python-format +msgid "" +"The way the ElGamal/AES+SessionTag " +"algorithm\n" +"works is by managing a set of random one-time-use 32 byte arrays, and " +"expiring\n" +"them if they aren't used quickly enough. If we expire them too soon, " +"we're\n" +"forced to fall back on a full (expensive) ElGamal encryption, but if we " +"don't\n" +"expire them quickly enough, we've got to reduce their quantity so that we" +" don't\n" +"run out of memory (and if the recipient somehow gets corrupted and loses " +"some\n" +"tags, even more encryption failures may occur prior to detection). With " +"some\n" +"more active detection and feedback driven algorithms, we can safely and " +"more\n" +"efficiently tune the lifetime of the tags, replacing the ElGamal " +"encryption with\n" +"a trivial AES operation." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:55 +#, python-format +msgid "" +"Additional ideas for improving Session Tag delivery are described on the\n" +"ElGamal/AES+SessionTag page." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:61 +msgid "Migrate sessionTag to synchronized PRNG" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:62 +#, python-format +msgid "" +"Right now, our ElGamal/AES+SessionTag \n" +"algorithm works by tagging each encrypted message with a unique random \n" +"32 byte nonce (a \"session tag\"), identifying that message as being " +"encrypted \n" +"with the associated AES session's key. This prevents peers from " +"distinguishing \n" +"messages that are part of the same session, since each message has a " +"completely \n" +"new random tag. To accomplish this, every few messages bundle a whole \n" +"new set of session tags within the encrypted message itself, " +"transparently \n" +"delivering a way to identify future messages. We then have to keep track" +" \n" +"of what messages are successfully delivered so that we know what tags \n" +"we may use." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:74 +msgid "" +"This works fine and is fairly robust, however it is inefficient in terms" +" \n" +"of bandwidth usage, as it requires the delivery of these tags ahead of \n" +"time (and not all tags may be necessary, or some may be wasted, due to \n" +"their expiration). On average though, predelivering the session tag costs" +" \n" +"32 bytes per message (the size of a tag). As Taral suggested though, that" +" \n" +"size can be avoided by replacing the delivery of the tags with a " +"synchronized \n" +"PRNG - when a new session is established (through an ElGamal encrypted \n" +"block), both sides seed a PRNG for use and generate the session tags on \n" +"demand (with the recipient precalculating the next few possible values \n" +"to handle out of order delivery)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:87 +msgid "Longer lasting tunnels" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:88 +msgid "" +"The current default tunnel duration of 10 minutes is fairly arbitrary, " +"though\n" +"it \"feels okay\". Once we've got tunnel healing code and more effective" +" failure\n" +"detection, we'll be able to more safely vary those durations, reducing " +"the\n" +"network and CPU load (due to expensive tunnel creation messages)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:95 +msgid "" +"This appears to be an easy fix for high load on the big-bandwidth " +"routers, but\n" +"we should not resort to it until we've tuned the tunnel building " +"algorithms further.\n" +"However, the 10 minute tunnel lifetime is hardcoded in quite a few " +"places,\n" +"so substantial effort would be required to change the duration.\n" +"Also, it would be difficult to maintain backward compatibility with such " +"a change." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:102 +msgid "" +"Currently, since the network average tunnel build success rate is fairly " +"high,\n" +"there are no current plans to extend tunnel lifetime." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:108 +msgid "Adjust the timeouts" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:109 +msgid "" +"Yet another of the fairly arbitrary but \"okay feeling\" things we've got" +" are the\n" +"current timeouts for various activities. Why do we have a 60 second " +"\"peer\n" +"unreachable\" timeout? Why do we try sending through a different tunnel " +"that a\n" +"LeaseSet advertises after 10 seconds? Why are the network database " +"queries\n" +"bounded by 60 or 20 second limits? Why are destinations configured to " +"ask for a\n" +"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a " +"peer to\n" +"reply to our request that they join a tunnel? Why do we consider a " +"tunnel that\n" +"doesn't pass our test within 60 seconds \"dead\"?" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:119 +msgid "" +"Each of those imponderables can be addressed with more adaptive code, as " +"well\n" +"as tunable parameters to allow for more appropriate tradeoffs between\n" +"bandwidth, latency, and CPU usage." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:125 +msgid "Full streaming protocol improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:128 +msgid "" +"Perhaps re-enable the interactive stream profile (the \n" +"current implementation only uses the bulk stream profile)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:134 +msgid "" +"Client level bandwidth limiting (in either or both directions on a " +"stream, \n" +"or possibly shared across multiple streams). This would be in addition to" +" \n" +"the router's overall bandwidth limiting, of course." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:141 +msgid "" +"Access control lists (only allowing streams to or from certain other " +"known \n" +"destinations)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:147 +msgid "" +"Web controls and monitoring the health of the various streams, as well \n" +"as the ability to explicitly close or throttle them." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:153 +#, python-format +msgid "" +"Additional ideas for improving the streaming library are described on the" +"\n" +"streaming library page." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:2 +msgid "Performance History" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:4 +#, python-format +msgid "" +"Notable performance improvements have been made using the techniques " +"below.\n" +"There is more to do, see the Performance " +"page\n" +"for current issues and thoughts." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:10 +msgid "Native math" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:11 +#: i2p2www/pages/site/about/performance/history.html:67 +#: i2p2www/pages/site/about/performance/history.html:82 +#: i2p2www/pages/site/about/performance/history.html:105 +#: i2p2www/pages/site/about/performance/history.html:133 +msgid "implemented" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:12 +#, python-format +msgid "" +"When I last profiled the I2P code, the vast majority of time was spent " +"within\n" +"one function: java.math.BigInteger's\n" +"modPow.\n" +"Rather than try to tune this method, we'll call out to\n" +"GNU MP - an insanely fast math library\n" +"(with tuned assembler for many architectures). (Editor: see\n" +"NativeBigInteger for faster public key " +"cryptography)" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:23 +msgid "" +"\n" +"ugha and duck are working on the C/JNI glue code, and the existing java " +"code\n" +"is already deployed with hooks for that whenever its ready. Preliminary " +"results\n" +"look fantastic - running the router with the native GMP modPow is " +"providing over\n" +"a 800% speedup in encryption performance, and the load was cut in " +"half. This\n" +"was just on one user's machine, and things are nowhere near ready for " +"packaging\n" +"and deployment, yet." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:32 +msgid "Garlic wrapping a \"reply\" LeaseSet" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:33 +msgid "implemented but needs tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:34 +msgid "" +"This algorithm tweak will only be relevant for applications that want " +"their\n" +"peers to reply to them (though that includes everything that uses " +"I2PTunnel or\n" +"mihi's ministreaming lib):" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:39 +msgid "" +"Previously, when Alice sent Bob a message, when Bob replied he had to do " +"a\n" +"lookup in the network database - sending out a few requests to get " +"Alice's\n" +"current LeaseSet. If he already has Alice's current LeaseSet, he can " +"instead\n" +"just send his reply immediately - this is (part of) why it typically " +"takes a\n" +"little longer talking to someone the first time you connect, but " +"subsequent\n" +"communication is faster. Currently - for all clients - we wrap\n" +"the sender's current LeaseSet in the garlic that is delivered to the " +"recipient,\n" +"so that when they go to reply, they'll always have the LeaseSet " +"locally\n" +"stored - completely removing any need for a network database lookup on " +"replies.\n" +"This trades off a large portion of the sender's bandwidth for that faster" +" reply.\n" +"If we didn't do this very often,\n" +"overall network bandwidth usage would decrease, since the recipient " +"doesn't\n" +"have to do the network database lookup." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:54 +msgid "" +"For unpublished LeaseSets such as \"shared clients\", this is the only " +"way to\n" +"get the LeaseSet to Bob. Unfortunately this bundling every time adds\n" +"almost 100% overhead to a high-bandwidth connection, and much more to" +"\n" +"a connection with smaller messages." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:60 +msgid "" +"Changes scheduled for release 0.6.2 will bundle the LeaseSet only when\n" +"necessary, at the beginning of a connection or when the LeaseSet changes." +"\n" +"This will substantially reduce the total overhead of I2P messaging." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:66 +msgid "More efficient TCP rejection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:68 +msgid "" +"At the moment, all TCP connections do all of their peer validation after\n" +"going through the full (expensive) Diffie-Hellman handshaking to " +"negotiate a\n" +"private session key. This means that if someone's clock is really wrong," +" or\n" +"their NAT/firewall/etc is improperly configured (or they're just running " +"an\n" +"incompatible version of the router), they're going to consistently " +"(though not\n" +"constantly, thanks to the banlist) cause a futile expensive cryptographic" +"\n" +"operation on all the peers they know about. While we will want to keep " +"some\n" +"verification/validation within the encryption boundary, we'll want to " +"update the\n" +"protocol to do some of it first, so that we can reject them cleanly\n" +"without wasting much CPU or other resources." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:81 +msgid "Adjust the tunnel testing" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:83 +msgid "" +"Rather than going with the fairly random scheme we have now, we should " +"use a\n" +"more context aware algorithm for testing tunnels. e.g. if we already " +"know its\n" +"passing valid data correctly, there's no need to test it, while if we " +"haven't\n" +"seen any data through it recently, perhaps its worthwhile to throw some " +"data its\n" +"way. This will reduce the tunnel contention due to excess messages, as " +"well as\n" +"improve the speed at which we detect - and address - failing tunnels." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:92 +msgid "Persistent Tunnel / Lease Selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:93 +msgid "" +"Outbound tunnel selection implemented in 0.6.1.30, inbound lease " +"selection \n" +"implemented in release 0.6.2." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:97 +msgid "" +"Selecting tunnels and leases at random for every message creates a large" +" \n" +"incidence of out-of-order delivery, which prevents the streaming lib from" +" \n" +"increasing its window size as much as it could. By persisting with the \n" +"same selections for a given connection, the transfer rate is much faster." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:104 +msgid "Compress some data structures" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:106 +msgid "" +"The I2NP messages and the data they contain is already defined in a " +"fairly\n" +"compact structure, though one attribute of the RouterInfo structure is " +"not -\n" +"\"options\" is a plain ASCII name = value mapping. Right now, we're " +"filling it\n" +"with those published statistics - around 3300 bytes per peer. Trivial to" +"\n" +"implement GZip compression would nearly cut that to 1/3 its size, and " +"when you\n" +"consider how often RouterInfo structures are passed across the network, " +"that's\n" +"significant savings - every time a router asks another router for a " +"networkDb\n" +"entry that the peer doesn't have, it sends back 3-10 RouterInfo of them." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:117 +msgid "Update the ministreaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:118 +msgid "replaced by full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:119 +msgid "" +"Currently mihi's ministreaming library has a fairly simple stream " +"negotiation\n" +"protocol - Alice sends Bob a SYN message, Bob replies with an ACK " +"message, then\n" +"Alice and Bob send each other some data, until one of them sends the " +"other a\n" +"CLOSE message. For long lasting connections (to an IRC server, for " +"instance),\n" +"that overhead is negligible, but for simple one-off request/response " +"situations\n" +"(an HTTP request/reply, for instance), that's more than twice as many " +"messages as\n" +"necessary. If, however, Alice piggybacked her first payload in with the " +"SYN\n" +"message, and Bob piggybacked his first reply with the ACK - and perhaps " +"also\n" +"included the CLOSE flag - transient streams such as HTTP requests could " +"be\n" +"reduced to a pair of messages, instead of the " +"SYN+ACK+request+response+CLOSE." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:132 +msgid "Implement full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:134 +msgid "" +"The ministreaming protocol takes advantage of a poor design decision in " +"the\n" +"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", " +"allowing what\n" +"would otherwise be an unreliable, best-effort, message based protocol to " +"be used\n" +"for reliable, blocking operation (under the covers, its still all " +"unreliable and\n" +"message based, with the router providing delivery guarantees by garlic " +"wrapping\n" +"an \"ACK\" message in with the payload, so once the data gets to the " +"target, the\n" +"ACK message is forwarded back to us [through tunnels, of course])." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:143 +#, python-format +msgid "" +"As I've said, having\n" +"I2PTunnel (and the ministreaming lib) go this route was the best thing " +"that\n" +"could be done, but more efficient mechanisms are available. When we rip " +"out the\n" +"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves " +"with an\n" +"I2CP that looks like an anonymous IP layer, and as such, we'll be able to" +"\n" +"implement the streaming library to take advantage of the design " +"experiences of\n" +"the TCP layer - selective ACKs, congestion detection, nagle, etc." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:2 +msgid "Performance" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:5 +msgid "" +"How does I2P work, why is it slow, and why does it not use my full " +"bandwidth?" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:7 +msgid "" +"Probably one of the most frequent things people ask is \"how fast is " +"I2P?\",\n" +"and no one seems to like the answer - \"it depends\". After trying out " +"I2P, the\n" +"next thing they ask is \"will it get faster?\", and the answer to that is" +" a most\n" +"emphatic yes." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:14 +msgid "" +"I2P is a full dynamic network. Each client is known to other nodes and " +"tests local known nodes for reachability and capacity.\n" +"Only reachable and capable nodes are saved to a local NetDB (This is " +"generally only a portion of the network, around 500-1000).\n" +"When I2P builds tunnels, it selects the best resource from this pool. For" +" example, a small subset of 20-50 nodes are only available to build " +"tunnels with.\n" +"Because testing happens every minute, the pool of used nodes changes " +"every minute.\n" +"Each I2P node knows a different part of the net, meaning that each router" +" has a different set of I2P nodes to be used for tunnels.\n" +"Even if two routers have the same subset of known nodes, the tests for " +"reachability and capacity will likely show different results, as the " +"other routers could be under load just as one router tests, but be free " +"if the second router tests." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:23 +msgid "" +"The above describes why each I2P node has different nodes to build " +"tunnels.\n" +"Because every I2P node has a different latency and bandwith, tunnels " +"(which are built via those nodes) have different latency and bandwidth " +"values.\n" +"And because every I2P node has different tunnels built, no two I2P nodes " +"have the same tunnel sets." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:29 +msgid "" +"A server/client is known as a \"destination\" and each destination has at" +" least one inbound and one outbound tunnel. The default is 3 hops per " +"tunnel.\n" +"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip" +" client-server-client." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:34 +msgid "" +"Each data package is sent through 6 other I2P nodes until it reaches the " +"server:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:40 +msgid "and on way back 6 different I2P nodes:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:47 +msgid "" +"As most traffic on I2P (www, torrent,...) needs ack packages until new " +"data is sent, it needs to wait until a ack package returns from the " +"server.\n" +"In the end: send data, wait for ack, send more data, wait for ack,..\n" +"As the RTT (RoundTripTime) adds up from the latency of each individual " +"I2P node and each connection on this roundtrip, it takes usually 1-3 " +"seconds until a ack package comes back to the client.\n" +"With some internals of TCP and I2P transport, a data package has a " +"limited size and cannot be as large as we want it to be.\n" +"Together these conditions set a limit of max bandwidth per tunnel of " +"20-50 kbyte/sec.\n" +"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, " +"the whole tunnel is limited to 5 kb/sec, independent of the \n" +"latency and other limitations." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:57 +msgid "" +"Due to encryption used and other setups in I2P (howto built up tunnels, " +"latency, ...) it is quite expensive in CPU time to build a tunnel. This " +"is \n" +"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels" +" to transport data. With a max of 50 kb/sec per tunnel, a destination " +"could \n" +"use roughly 300 kb/sec traffic combined ( in reality it could be more if " +"shorter tunnels are used with low or no anonymity available).\n" +"Used tunnels are discarded every 10 minutes and new ones are built up.\n" +"This change of tunnels (and sometimes clients that shutdown hard due to " +"usage of \"shut down at once\" or situations where there is power loss) " +"does \n" +"sometimes break tunnels and connections, as seen on the IRC2P Network in " +"loss of connection (ping timeout) or on when using eepget." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:66 +msgid "" +"With a limited set of destinations and a limited set of tunnels per " +"destination, one I2P node only uses a limited set of tunnels across other" +" I2P nodes.\n" +"For example, if an I2P node is \"hop1\" in the small example above, we " +"only see 1 participating tunnel originating from the client.\n" +"If we sum up the whole I2P network, only a rather limited number of " +"participating tunnels could be built with a limited amount of bandwidth " +"all together.\n" +"If one distributes these limited numbers across the number of I2P nodes, " +"there is only a fraction of available bandwidth/capacity available for " +"use." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:73 +msgid "" +"To remain anonymous one router should not be used by the whole network " +"for building tunnels.\n" +"If one router does act as a tunnel router for ALL I2P nodes, it becomes a" +" very real central point of failure as well as a central point to grab " +"IPs and data from the clients. This is not good.\n" +"I2P attempts to spread the load across a lot of I2P nodes because of this" +" reason." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:79 +msgid "" +"Another point is the full mesh network. Each connection hop-hop utilizes " +"one TCP or UDP connection on the I2P nodes. With 1000 connections, one " +"sees \n" +"1000 TCP connections. That is quite a lot and some home and small office " +"routers (DSL, cable,..) only allow a small number of connections (or just" +" go mad if you use more than X connections).\n" +"I2P tries to limit these connections to be under 1500 per UDP and per TCP" +" type.\n" +"This limits the amount of traffic routed across your I2P node as well." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:86 +msgid "" +"In summary, I2P is very complex and there is no easy way to pinpoint why " +"your node is not used.\n" +"If your node is reachable and has a bandwidth setting of >128 kbyte/sec " +"shared and is reachable 24/7, it should be used after some time for " +"participating traffic.\n" +"If it is down in between, the testing of your I2P node done by other " +"nodes will tell them: you are not reachable. This blocks your node for at" +" least \n" +"24h on other nodes. So, the other nodes which tested you as down will not" +" use your node for 24h for building tunnels. This is why your traffic " +"will \n" +"be lower after a restart/shutdown for a minimum of 24h." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:94 +msgid "" +"Also: other I2P nodes needs to know your I2P router to test it for " +"reachability and capacity. It takes time for other nodes to get known to " +"your node. \n" +"It will be faster if you use I2P and build more tunnels, e.g. use a " +"torrent or www for some time." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:99 +msgid "Performance Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:101 +#, python-format +msgid "" +"For possible future performance improvements see\n" +"Future Performance Improvements." +msgstr "" +